Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Tools used to monitor RICEF objects in production? Tips??

Former Member
0 Kudos

Hi,

For a functional consultant in a support role, what are tools/t-code used for?

1. IDOC

2. BAPI

3. Enhancement

What are monitoring processes?

Tips/Hints in working on support activities???

Please help clariy my doubts

Monica

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi,

I try to answer the questions but might not satisfies you.

1. WE05, BD20, BD87, WE20, SALE, and some more

2. The t-code is BAPI and SE37 since BAPI is in a form of a Function Module

3. Enhancement could be found in t-code SMOD and CMOD

Regards,

Teddy

3 REPLIES 3

Former Member
0 Kudos

Hi,

I try to answer the questions but might not satisfies you.

1. WE05, BD20, BD87, WE20, SALE, and some more

2. The t-code is BAPI and SE37 since BAPI is in a form of a Function Module

3. Enhancement could be found in t-code SMOD and CMOD

Regards,

Teddy

0 Kudos

Hi Terry,

Thansk for your hints.

Can you elaborate the use of those T-code?? I am a functional person. Have very little idea about these tools. Please correct me if i am wrong. I know a bit that WeXX are used to search for IDOC and their statuses.

What about BAPI when they are used instead of IDOC for interfaces? Do we use BAPI, SE37, SE24 to monitor if the message get posted??

What about. SALE, what are the specific t-code under SALE tree that are normally used?? What object that we would use this SALE to monitor?? and BD20???

Please excuse my limited knowledge.. I would appreciate your clarification

Monica

0 Kudos

Hi Monica,

Sorry, but my name is Teddy. Please use 'd'

I try to describe the T-Code based on my experience.

WE05 is IDoc list where you can list the inbound and outbound IDoc messages. You can see the IDoc No, status, basic type, and many more. If the system have just sent an outbound IDoc or received an inbound IDoc, the IDoc will be listed there. You can double click at the IDoc No to see the contents and status records.

BD20 is used to process IDoc with status 'Ready for Transfer' (to post). This is mainly used for inbound IDoc. For example the configuration for message type A1 is set to not immediate processing. This means when the IDoc is received by system, it is not directly processed. You might have a periodic background job that runs BD20 to process the IDoc. You can also manually run the T-Code.

BD87 is alike with BD20 and WE05. Because here you can list the IDoc based on its status and reprocess it (in case of error). Outbound IDocs are also available here.

WE20 is used to specify partner profiles and the outbound/inbound parameter. Partner profile means the partner of your system where you send outbound IDoc to or receive inbound IDoc from. Usually this is set up by Basis Team. And the parameter for outbound/inbound is set by Development Team.

SALE is the main menu for IDoc. Here you can do almost all things related to IDoc. From the partners, messages, messages configurations, customizations, monitoring, error handlings, and more. For support role, you might only need to check the monitoring and error handling. But I'm not familiar with those.

BAPI is a FM that is used by IDoc to post the data. IDoc only contains the data to be posted and the system will call a configured FM to process and post it. The posting usually uses BAPI. With SE37 you can check the code of FM used for IDoc processing.

I have no idea in what way SE24 relate to IDoc because SE24 is used to maintain Class (an object like in java). Using BAPI, SE37, and SE24; you can't check the message status. Use WE05 for this purpose.

About SALE and BD20, please check the explanation above. I can't tell the t-code normally used because I'm also not sure.

Regards,

Teddy