COR6 confirmation error " Batch was distributed, Product. date can only be changed by batch master.

[former_member609925]

Hi Expert

Business user getting the error "Batch was distributed, Product. date can only be changed by batch master" during the process order confirmation via COR6. User update the manually production date in MSC2n transaction so then confirmation done but again COGI trigger same error.

Could you please guide me how I can resolve this issue.

Thank you in advance.

[DominikTylczyn · Accepted solution]

Hello syed786

The message VBW009 is generated in form routine CHECK_MHD, include MM07MMHD, line 476:

    CALL FUNCTION 'VB_CHRG_BATCH_DIST_STATUS_GET'
      EXPORTING
        i_matnr                    = frs_matnr
        i_charg                    = frs_charg
        i_werks                    = frs_werks
      IMPORTING
        e_change_local_fields_only = lv_change_local_fields_only
      EXCEPTIONS
        no_material                = 1
        no_batch                   = 2
        no_plant                   = 3
        inconsistency              = 4
        OTHERS                     = 99.
    IF NOT sy-subrc IS INITIAL.
      MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
              WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
  ENDIF.

  IF NOT xmchx-charg IS INITIAL AND
         xmchx-rmcha IS INITIAL.
*** Verprobung eingegebenes HSDAT gegen Chargenstammsatz ***************
    IF NOT omchx-hsdat IS INITIAL AND
           omchx-hsdat NE dm07m-hsdat_input.
      SET CURSOR FIELD 'DM07M-HSDAT_INPUT'.
*- no change allowed due to distribution status
      IF NOT lv_change_local_fields_only IS INITIAL.
*! Distributed batch. Production date only changeable in batch master
        MESSAGE e009(vbw).
      ENDIF.

The message is active only if lv_change_local_fields_only variable is not initial. The variable is originally set by VBWC_BATCH_DIST_STATUS_GET function. You can put a break-point there and analyze your case.

You can also check ALE_BATCHES_SENT table, that holds batches distributed to other systems. According to my understanding of VBWC_BATCH_DIST_STATUS_GET function logic production data can't be changed if the batch is distributed to other systems.

Best regards

Dominik Tylczynski

[subhrantbal]

Hi Syed ,

I think the batch movement is happening from any other sources like WM or EWM.

If so you need to check with EWM consultant about this inconsistency.

there might be many reasons for this.

regards

Subhrant

[DominikTylczyn]

Hello syed786

I'm afraid something is not right with your process. Error message VBW009 "Batch was distributed. Product. date can only be changed in batch master" tells that the batch was received / replicated from another system. Therefore you can't change production date in the receiving system. The date can only be changed in the source system. If your batches are maintained centrally and distributed to another systems, you shouldn't change production date in the batch receiving system with production confirmation.

However if you are 100% sure that you have to change batch production date with COR6 you can remove the batch from the ALE_BATCHES_RECP table. That's where received batches are stored. An entry in the ALE_BATCHES_RECP table prevents any changes to batch production date and other centrally maintained batch fields.

Best regards

Dominik Tylczynski

[former_member609925]

Hi Dominik, thanks for the quick solution

I check there is no entry in ALE_BATCHES_RECP table, from business side only Goods Receipt done via COR6 and other than 101 movements, 261 movements are showing in COR3->Goto -> List-> Document goods movement. If I check in MB51 t-code here it showing the 101 movements.

I am new to PP so I am not understanding what is the reason behind it, could you please help me what would be cause.

Thank you in Advance.