Hello, I have a dump in transaction MFBF

[David_mT]

Dump in transaction MFBF when I confirm quantity  

PERFORM_NOT_FOUND      CX_SY_DYN_CALL_ILLEGAL_FORM  SAPLV01F 

This is because of the non creation of subroutine CHMVS_600 in program saplv01f

The line of the code is   

PERFORM (distform) IN PROGRAM saplv01f. 

But same foms exist CHMVS_001, CHMVS_002, CHMVS_003

Do you know how avoid this error ?

But why the system check it as it does not exist

I create a new procedure in "Define batch determination Quantity Proposal Procedure" 600 in custo 

Extract standard code source

IF NOT gv_receipt IS INITIAL.  
 IF xkondh-chmvs >= 600. 
           distform-prenam = k_prenam.
          distform-suffix = xkondh-chmvs.
          PERFORM (distform) IN PROGRAM saplv01f.
ELSE. "If xkondh-chmvs >= 600  ""1234668
           READ TABLE disqty INDEX 1.
         IF sy-subrc IS INITIAL.
           disqty-quantity = quan_to_dis.
            MODIFY disqty INDEX 1.
        ENDIF.
ENDIF. "If xkondh-chmvs >= 600

[Dominik_Tylczynski · Accepted solution]

Hello @David_mT 

It looks like you are using a batch determination quantity proposal procedure 600 which is not defined in your system. That is strange as procedure 600 is part of the standard delivery:

************************************************************************
* FORM CHMVS_600
************************************************************************
* Routine to distribute the available quantities of batches.
* The distribution is an example for a TOP-DOWN distribution
* with regard to the sort sequence.
* To set up your own distribution rules, sort the following table
* according to your requirements.
*
* Structure of internal table DISQTY (significant fields):
* --------------------------------------------------------
*    DATA: BEGIN OF DISQTY OCCURS 0,
*            MATNR     LIKE BDBATCH-MATNR,    -> material number
*            CHARG     LIKE BDBATCH-CHARG,    -> batch number
*            WERKS     LIKE BDBATCH-WERKS,    -> plant
*            LGORT     LIKE BDBATCH-LGORT,    -> storage location
*            AVAL_QUAN LIKE V01FDK-VRFMG,     -> available quantity
*            QUANTITY  LIKE BDBATCH-MENGE,    -> target quantity
*            RES_TABIX LIKE SY-TABIX.         ->internal use
*    DATA: END OF DISQTY.
*
* Additional fields for distribution:
* -----------------------------------
* NO_OF_SPLIT -> The number of possible batch quantity splits
* QUAN_TO_DIS -> The quantity to be distributed (ordered quantity)
*
* Restrictions!
* -------------
* 1) Don't add or delete any entries from the internal table
* 2) Don't modify fields MATNR, CHARG, WERKS, LGORT, AVAL_QUAN and
*    RES_TABIX.
* 3) Don't change values of NO_OF_SPLIT and QUAN_TO_DIS
* 4) The only field that can be modified is the DISQTY-QUANTITY field
************************************************************************
FORM chmvs_600.

* BEGIN: get valuation type from PO line item
* the logic copied from the email. Can't verify it without access to Yara system.
* Assuming it is correct

  DATA: lv_delnr  TYPE lips-vbeln,
        lv_delpos TYPE lips-posnr,
        lv_ebeln  TYPE ekpo-ebeln,
        lv_ebelp  TYPE ekpo-ebelp.

...

Best regards

Dominik Tylczynski

[David_mT · Accepted solution]

Thanks for the answer, finaly we create an enhancement to add the form missing FORM chmvs_600.

[Lakshmipathi]

MFBF is a standard transaction and in that if system triggers some dump, it could be due to incorrect custom validation for that process.

Is the issue coming for all plants or only for a selected plant? Did you check the dump analysis via st22 where you have some tabs "Error analysis" and "Information on where it terminated" 

[ArunJacob]

Hi David,

xkondh-chmvs contains 600, which results in PERFORM CHMVS_600 IN PROGRAM SAPLV01F.

this table: TCHMVS

look for entries with 600.

Thanks,

Arun