How to find if ZFM is affecting to standard t-code ?

[vinayad]

Hi all,

In VA02, when the sales order# enters for multiple items the MBDAT value is varying(After save).

I have created ZFM for Sales Order change to other requirement (had put breakpoint to check whether it is causing but not stopped).

Here, I would like to know where exactly the error is causing or if you have any ideas to reach it, please share it.

Any help would be appreciated!

[Sandra_Rossi]

If ZFM runs in an update task, start the Update Task Debug otherwise it won't stop.

[vinayad]

Hi sandra.rossi

Thanks for your response!

I debugged VA02 till the value updates but nowhere I came across this ZFM.

And I tried by commenting whole ZFM then in VA02 the MBDAT values are displaying same.

[Sandra_Rossi]

Because of the title, I thought your Z function module was the cause of the issue. No need to talk about it then.

[Sandra_Rossi]

Forget my last comment, I understood incorrectly your comment. Did you activate the Update Task debug correctly?

If it still doesn't work, I recommend that you make a short dump when your Z FM is called to see the call stack (MESSAGE '' TYPE 'X').

[vinayad]

Hi sandra.rossi

I tried by putting this -> Message 'Test dump' type 'X'. (I put breakpoint here and not stopped but the wonder is MBDAT value is not updated using offset, all the values are same).

So, in ZFM I have used BAPI and in BAPI it is making trouble(MBDAT value is varying).

[Sandra_Rossi]

It's a short dump, it doesn't make you stop at the breakpoint. Short dumps are in ST22.

[vinayad]

Hi sandra.rossi

Yes in ST22, it is displaying the same dump which I have mentioned type 'X'.

[Sandra_Rossi]

In the short dump, you have a call stack, it shows which programs call ZFM.

[vinayad]

Hi sandra.rossi

I found in my ZFM, it's calling BAPI there it is update varying.

So, how can I control this and make it correct?

[Sandra_Rossi]

In the call stack, you can see what calls your ZFM, so you should be able to understand the context how it's called (update task, RFC, etc.) and debug it.

Note that if you can't understand the context, you can also add an endless loop in ZFM like below, then you can debug via SM50/SM66 (solution often discussed in the forum):

IF sy-datum = '20210206' AND sy-uname = 'VINAYAKD'.
  DO.
  ENDDO.
ENDIF.

[Sandra_Rossi]

Your question is imprecise. Lot of context missing. The little information is even misleading. You must find a way to reproduce the problem (each time you run it). Then you have a chance to troubleshoot it.

[VXLozano]

By definition, Z function modules do NOT affect standard code. Read your FM, learn what does it do, and check if it changes that value. If it doesn't, it doesn't.

Try to determine since when this behaviour is occurring, and check for transports just before. Some of them will contain an enhancement implementation that affects that field.

[vinayad]

Hi vicen.lozano

Thanks for your response!

Normally my ZFM does MBDAT field update using offset number for SO#

This behavior is happening since, after I released this ZFM

[VXLozano]

Ok, after reading the comments on the initial post, your question was not the proper one XD

Again, your FM does NOT affect the source code, but it maybe affects the data... If you have commented the whole code and the wrong behaviour stills there, then there is another program object that is changing that value.

Try to find it by doing a reference use check on the field (SE11, your table, double click on your field, and in the popup window, look for the reference use button (box with few arrows spiking out). You will be amazed about how many you will find.
Put a break-point on everyone of them, and execute the process again (remember the update option Sandra Rossi pointed).

Good luck.

[Abinathsiva]

Hi,

try with following exits or BADI implementation based on requirement.

Enhancement/ Business Add-in Description

Enhancement

SDTRM001 Reschedule schedule lines without a new ATP check

V45A0001 Determine alternative materials for product selection

V45A0002 Predefine sold-to party in sales document

V45A0003 Collector for customer function modulpool MV45A

V45A0004 Copy packing proposal

V45E0001 Update the purchase order from the sales order

V45E0002 Data transfer in procurement elements (PRreq., assembly)

V45L0001 SD component supplier processing (customer enhancements)

V45P0001 SD customer function for cross-company code sales

V45S0001 Update sales document from configuration

V45S0003 MRP-relevance for incomplete configuration

V45S0004 Effectivity type in sales order

V45W0001 SD Service Management: Forward Contract Data to Item

V46H0001 SD Customer functions for resource-related billing

V60F0001 SD Billing plan (customer enhancement) diff. to billing plan

Business Add-in

BADI_SD_SCH_GETWAGFZ Scheduling Agreement: Read WAGFZ from S073

BADI_SD_V46H0001 SD Customer functions for resource-related billing

[former_member749473]

hi abinath

can u say where does the bussiness logic is stored in sap?