cancel
Showing results for 
Search instead for 
Did you mean: 

ABAP Consistency Check Production Versions

GDeConinck
Explorer
0 Kudos

Hi Experts,

To fulfill the requirement of our customer we created an upload tool for master date which creates BoM's, Routings and Production Versions in one go.

Creation of these objects works just fine, but there is one problem with the production versions. We are using CM_FV_PROD_VERS_DB_UPDAT as function module and are entering all the required information.

Now our issue is the consistency check. We update PRFG_S, PRFG_F and the PRDAT, but after saving and running the MRP, the BoM is not found. When we do the consistency check manually in transaction C223 it works perfectly.

Could you please help us out to fix this issue on how to do the Consistency Check for this Production Version?

Thank you very much!

KR,

Accepted Solutions (0)

Answers (2)

Answers (2)

ninad_narad
Active Participant
0 Kudos

Hello Caetano & Guy,

I used the same FM to create PVs in mass.

The MKAL table is filled correctly but there is one issue with MARC-VERKZ field which is for version indicator in material master. This field is not getting checked even though I have a valid PV for the material.

Is there any solution for this issue? Can we check this indicator by passing a value in FM.?

Regards,

Ninad

fahim_am
Explorer
0 Kudos

Hi,

I am also facing same issue. After mass upload in C223, PVs are not checked for consistency and in material master version indicator (MARC-VERKZ) is not checked.

Please let me know the solution.

Thanks in advance.

Regards,

Fahim

0 Kudos

Is there any soluction to handle MARC-VERKZ as X after mass create PVs with BAPI?

ninad_narad
Active Participant
0 Kudos

hi,


We resolved this issue by running a correction report after all the production version load are completed, we added it in the code itself of the load program. The correction report details are mentioned in note 856937.
I hope this resolves your issue.


Regards,

Ninad

Caetano
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Guy

Function module CM_FV_PROD_VERS_DB_UPDAT is not released, which means that it was not developed to be used in custom programs, so these kind of problems may happen when you use it outside SAP standard transactions.

Did you try to compare the values on table MKAL when you create the production in C223 and when you create it with this function module? Anything different?

Regards,

Caetano

GDeConinck
Explorer
0 Kudos

Hello Caetano,

Thank you for your answer. The MKAL-table is correctly filled and is 100% the same as a manually created Production Version. Unfortunately, when I look at the details, I notice at the bottom that some fields are not filled in, fields that reference to table MKAL_EXPAND. I was hoping that a solution could be provided on how to fix this during the creation of the production version, how to add the fields to that structure.

As there is no standard BAPI available for the Production Version, we feld 'obliged' to use this one. Just hoping to take the last bump in the ride.

Kind Regards,

Guy De Coninck