DevOps and System Administration Discussions
Dive into SAP DevOps and system administration. Join discussions to collaborate on optimizing workflows, share knowledge, and leverage resources effectively.
cancel
Showing results for 
Search instead for 
Did you mean: 

BD87 not see any transactions

former_member709286
Participant
0 Kudos

Hi Expert:

I can access t.code BD87 but I not see any transactions at all.
The same thing as WE02, WE05 that I can access but I not see any IDOC.

Pls advise and thanks in advance.

1 ACCEPTED SOLUTION

VeselinaPeykova
Active Contributor
0 Kudos

manthana99

you misunderstood me. By customizing client I meant a client where you do not have transactional data, you only use it for configuring the system, which means that you have no IDOCs in it (no entries in EDIDC).

If there are no entries in EDIDC, it means that there are no IDOCs for you to reprocess. If there are entries - try selecting the IDOC by IDOC number. Again, make sure that you do not have any other selections applied in BD87.

I am confused by the explanation about SLG1. SLG1 is a general transaction to view application logs. Why do you assume that if there are any errors that they will be related to IDOC issues which can be solved by reprocessing?

Assuming that the errors in SLG1 are not only related to IDOCs, you resolve the issues case by case (of course, if you have the relevant knowledge on the subject and if you are allowed to fix the specific problem, otherwise you ask a colleague who is responsible for the area to assist you).

In my opinion, it is not correct to assume that all errors in SLG1 can be fixed just by reprocessing something (if things were so easy, many consultants will be unemployed).

Frankly, I do not use SLG1 to check for problems with IDOCs, this is what BD87, WLF_IDOC, etc. are for (sometimes SE16 is the best option for reporting).

Whether you are supposed to have any IDOCs in this client and if this is a customizing client - the best way to find out is to ask your colleagues what this client is used for. You can, of course check the client settings in SCC4, but this is no guarantee, settings can be easily changed.

View solution in original post

3 REPLIES 3

VeselinaPeykova
Active Contributor
0 Kudos

You did not provide enough information that could make it possible for people with no access to your system and to your screen to help you, which means that my suggestions will be really generic and seem somewhat insulting (which is not my intention).

1. Check if in the system where you execute the transactions there are any IDOCs (it can be that you run the transaction in a customizing client, for example, where it is not expected to have any IDOCs). Use EDIDC table in SE16 and check the number of entries.

2. If there are entries in in EDIDC, but you see nothing in WE05, WE02, etc. - check your selection criterion against the entries in EDIDC - is your selection correct? Quite often I forget to delete the dates when I search by IDOC number. Take an entry from EDIDC, use it in WE02, make sure to delete all other selection criteria.

3. Check for authorization problems - STAUTHTRACE or ST01.

4. If still no luck and if other users can view the same IDOCS - debug.

0 Kudos

Hi Veselina:

I just checked the EDIDC. But no transactions on current year at all.

Actually when I display transaction logs on SLG1 and show errors. I would like to go to BD87 and Reprocess. But when I display with criteria all months , the system just not show anything.

This is screen on SLG1

This is screen on BD87

So per your guideline maybe it is customizing client.

In this case , pls advise

1.how to reprocess the error transactions.

2. How to know this is customizing client.

Looking forward for your guidance and thanks in advance.

VeselinaPeykova
Active Contributor
0 Kudos

manthana99

you misunderstood me. By customizing client I meant a client where you do not have transactional data, you only use it for configuring the system, which means that you have no IDOCs in it (no entries in EDIDC).

If there are no entries in EDIDC, it means that there are no IDOCs for you to reprocess. If there are entries - try selecting the IDOC by IDOC number. Again, make sure that you do not have any other selections applied in BD87.

I am confused by the explanation about SLG1. SLG1 is a general transaction to view application logs. Why do you assume that if there are any errors that they will be related to IDOC issues which can be solved by reprocessing?

Assuming that the errors in SLG1 are not only related to IDOCs, you resolve the issues case by case (of course, if you have the relevant knowledge on the subject and if you are allowed to fix the specific problem, otherwise you ask a colleague who is responsible for the area to assist you).

In my opinion, it is not correct to assume that all errors in SLG1 can be fixed just by reprocessing something (if things were so easy, many consultants will be unemployed).

Frankly, I do not use SLG1 to check for problems with IDOCs, this is what BD87, WLF_IDOC, etc. are for (sometimes SE16 is the best option for reporting).

Whether you are supposed to have any IDOCs in this client and if this is a customizing client - the best way to find out is to ask your colleagues what this client is used for. You can, of course check the client settings in SCC4, but this is no guarantee, settings can be easily changed.