Material Changes not getting transferred to APO

[shailendra_jain4]

Hi All,

Whenever we use MM02 transaction and make changes to material the changes are getting reflected in APO system

But when use the FM 'MATERIAL_MAINTAIN_DARK' to update the material seems the change pointer is not getting triggered and therefore no update in APO system.

For change pointer MATMAS is checked. Do I also need to to check CIFMAT? Or is there any other issue?

Regards,

Shailendra

[shailendra_jain4 · Accepted solution]

Okay, got it thanks all for generous help

Here's I solved it.

I saw for my application: ND-APO (Tx: BF31) the FM triggered was NDPLG_APO_001_00001250_MAT. In this FM the

CALL FUNCTION 'CIF_MATERIAL_OUTBOUND'
            IN UPDATE TASK

was not happening from my custom code as there was no explicit commit work.

I just added a commit work and it worked also I think instead of MATERIAL_MAINTAIN_DARK I could have used BAPI_MATERIAL_SAVEDATA.

[shailendra_jain4]

Any idea people??

[Former Member]

Hi Shaildendra,

Can you paste the code where you are calling the FM MATERIAL_MAINTAIN_DARK.

Regards,

Kannan

[shailendra_jain4]

Hi Kannan,

It goes something like this:

CALL FUNCTION 'MATERIAL_MAINTAIN_DARK'
       EXPORTING
         flag_muss_pruefen   = flag_muss_pruefen
         sperrmodus          = sperrmodus
         max_errors          = max_errors
         p_kz_no_warn        = p_kz_no_warn
         kz_prf              = kz_prf
         kz_verw             = kz_verw
         kz_aend             = kz_aend
         kz_dispo            = kz_dispo
         kz_test             = ok_test
         no_database_update  = no_database_update
         call_mode           = call_mode
         call_mode2          = call_mode2
         user                = sy-uname
         suppress_array_read = suppress_array_read
         flg_mass            = flg_mass
       TABLES
         amara_ueb           = imara_ueb1
         amakt_ueb           = imakt_ueb1
         amarc_ueb           = imarc_ueb1
         amard_ueb           = imard_ueb1
         ambew_ueb           = imbew_ueb1
         amvke_ueb           = imvke_ueb1
         amarm_ueb           = imarm_ueb1
         amlgt_ueb           = imlgt_ueb1
         amlgn_ueb           = imlgn_ueb1
         ae1cucfg_ueb        = ie1cucfg_ueb1
         ae1cuins_ueb        = ie1cuins_ueb
         ae1cuval_ueb        = ie1cuval_ueb1
         ae1cucom_ueb        = ie1cucom_ueb1
         amfieldres          = imfieldres1
         amerrdat            = izmerrdat1
       EXCEPTIONS
         kstatus_empty       = 1
         tkstatus_empty      = 2
         t130m_error         = 3
         internal_error      = 4
         too_many_errors     = 5
         update_error        = 6
         OTHERS              = 7.

[Former Member]

Hi Shaildendra,

Try by Commenting the line no_database_update  = no_database_update

Regards,

Kannan

[shailendra_jain4]

Hi Kannan,

value for no_database_update is space so it won't really matter. When i run the custom code I can see material updated through MM03 in ECC system.

Regards,

Shailendra

[Former Member]

Hi Shaildendra,

Can you test the function module in Se37 by giving the same entries in AMERA_UEB.

Check any execptions are triggered.

Regards,

Kannan

[former_member216565]

Hi Shailendra,

When you update through FM 'MATERIAL_MAINTAIN_DARK', as you said,it is updating. System should create change document for that. The same can be seen through Environment->Display Changes. So, i would suggest you to call this FM 'CHANGE_POINTERS_CREATE' and create the Change pointer manually for that change document. This may solve your problem.

Thanks

Santosh KB.