Help needed in debugging EDQA

[ravi_gupta1]

Hi All,

We have implemented EDQA functionality at our client which is supposed to confirm a back order on the basis of GR or sales order quanitity reduction. However system is not able to confirm specific type of orders through EDQA. There are no messages generated and upon displaying EDQA results, line item will be shown as unconfirmed only. No more details is available in BOP_Monitor transaction.

Could some one help us in debugging EDQA process with event as stock increment through MB1C.

Thanks in advance for help.

RG

[former_member458819]

Use Transaction Code:/SAPAPO/EDQA_OS

Sunil

[ravi_gupta1]

Thanks Kiru and Sunil. We have tried simulation already but it is not taking us to the debugging.

@Vedant: We have tried to debug FM /sapapo/edqa_determine but we didn't get desired output. Also do we really need to stop the CIF queues in order to debug EDQA?

We need to debug below objects to analyze the issue as why sales order is not being confirmed.

Class: /SAPAPO/CL_EDQA_PROCESS

Method: GET_WL_EDQA

Any help would be highly appreciated in this direction.

Thanks,

RG

[babu_kilari4]

Hi RaviGupta,

1) Set an entry in CFC2 transaction in ECC ( Recording option should be set as R )

2) Post the stock or reduce the quantity in demand element

3) You can log on to APO system and see that there is a queue available in NOEXEC status

4) Start debugging the queue by choosing the Edit Menu -> Debug LUW

5) Make sure that you're actually setting the external debugger here and press F8

6) Most importantly, since EDQA programming is completely workflow driven, so you would have an entry in SM58 ( tRFC transaction ).

7) Select the tRFC entry and debug the SM58 entry and it will take you to the relevant subroutines and function modules of EDQA.

Hope this helps.

Babu Kilari

[ravi_gupta1]

Hi Babu,

Thanks for your reply. We have a question about step 6. Do we need to add one step in workflow for infinite loop so that system will make an entry in SM38 for workflow.

Thanks again.

RG

[babu_kilari4]

Hello Ravigupta,

Did you set the update debugging option ? You should use the update debugging option there and also, there must be a checkbox next to it that says "Stop workflow" or something. Don't remember the exact name. Tick that, you will see an entry in SM58. Also, make sure that the background user that was setup for EDQA ( usually it would be WF-BATCH ) is a dialogue user. If it is not, you should change it to DIALOG type to get this done.

Please close the thread if this helps.

Babu Kilari

[ravi_gupta1]

Hi Babu,

Thanks for you answer. We have tried to execute the steps as you have mentioned but debugger doesn't stop at the desired class/ method. We are still trying to re-execute the same steps. Till the time, let the message remain in open status.

Thanks,

RG

[Former Member]

Hello RG,

We can stop CIF queues and debug function module /sapapo/edqa_determine.

Inside FM, EDQA trigger logic is implemented on the basis of activity type.

A case is implemented on "iv_action" which referred to activity type and for activity type STC i.e. "Change in stock data" debug when iv_action is "/sapapo/cl_edqa_c=>act_stc".

Thanks,

Vedant Pathak

[Former Member]

Hi Ravi,

Did you try the EDQA simulation using t.code - /sapapo/edqa_os ? . This should help you track down the issue, you have debugging option also in this simulation tool.

Rgds,

Kiru

[ravi_gupta1]

Also would like to share some more information about the issue from technical side.

Whenever the Stock is getting updated in ECC, the  below object is triggering the Workflow in APO system.

Object Type:      CL

Object:                 /SAPAPO/CL_EDQA_PROCESS

Event:                   EDQA

Workflow:           WS34500011 Event-Driven Quantity Assignment (EDQA)

Thanks,

RG