cancel
Showing results for 
Search instead for 
Did you mean: 

How to secure consistency of field MARC-PSTAT?

DanielP
Active Participant
0 Kudos

Just came across this situation.

Imagine that you start by creating a material in table MARA (Basic Data).

Then subsequently you extend it to table MARC (Purchasing).

Then afterwards you extend it to table MLGN (Warehouse views) where you state only Warehouse Number (no Plant).

In this case field MARC-PSTAT will not be updated with maintenance status "S" (Warehouse management).

(NB: we are aware of ZRMMMSTAT from Note 113966 to fix inconsistency between MARA/MARC maintenance status,

but this does not solve this scenario with MARC/MLGN).

Any ideas how to solve this problem?

Many thanks,

/Daniel


Accepted Solutions (1)

Accepted Solutions (1)

JL23
Active Contributor
0 Kudos

In general you can create the warehouse view prior to any plant view if you distribute the creation of material masters(theoretically you could even begin with the WM view), so an update would not even technically be possible in that case.

If the user enters the plant then he enables at least SAP to validate the correctness and existence and subsequently SAP can update the status.

In data migrations I always decide myself which status I submit.

I have not yet tested the manual case, but I trust you, and I see no chance how an update of MARC could be forced. Have you seen OSS note 2145027 , not quite easy to understand but certainly valuable information on the status updates. I found it last week and distributed it to my colleagues from the migration team.

Answers (6)

Answers (6)

Former Member
0 Kudos

This message was moderated.

DanielP
Active Participant
0 Kudos

Found the solution and sharing it with you all, in case of LSWM using method "IDOC" (Message Type: MATMAS; Basic Type: MATMAS03) it is just a matter of maintaining Segment/Field:

E1MARCM     Master material C segment (MARC)

STAT              Maintenance status

Rule:               Constant

Code:              E1MARCM-PSTAT = 'S'.

As well as all other needed Segment/Fields from:

E1MLGNM     Master material material data per warehouse number (MLGN)

@Jürgen L: 2145027 - FAQ: Maintenance status in data transfer placed me in the right track, thanks a lot.

/Daniel

DanielP
Active Participant
0 Kudos

Thank you all, SAP explains this behaviour in a Wiki, we are not totally convinced here because this should be possible in LSMW using other than method "Recording" (calling with MM01). We will question SAP on this.

2056054 - Maintenance Status S "Warehouse management" not getting
updated in table MARC

/Daniel

jagdeepsingh83
Active Contributor
0 Kudos

Are you using direct input program in LSWM ? if yes make sure you check   Warehouse Management View filed as X. This will transfer S indicator to the database otherwise it may skip it .. I found below note which is may be useful for you to understand

67616 - Direct input material master - maintenance status

Former Member
0 Kudos

You can correct the activation of maintenance status as per requirement, before that you need to move all

the existing Wm stock nill by moving somewhere or posting to do nill. then active and check the same.

Sanjeet

DanielP
Active Participant
0 Kudos

Do you know how to make sure that this does not happen in the first place?

any correction program from SAP AG for this purpose?

We know that if we go into MM01 as a 4th step and create (again!) the WM view by stating the Plant/Warehouse Number combination then "S" will be added into MARC-PSTAT, but why would we have to be forced to do such step?

/DPe

Former Member
0 Kudos

If you know the 4th step, then you should know about, user can do the mistake at any step. So first you need to define the process, how many views need to be maintain. as view maintained status would be update accordingly. This is not forced step this is as per requirement, need to active basic fields.

JL23
Active Contributor
0 Kudos

Are you talking about MM01 manual creation or about creation by other means like IDoc, BAPI, Batch Input?

DanielP
Active Participant
0 Kudos

Issue occurs both with MM01 and LSMW using IDOC method (Message Type: MATMAS; Basic Type: MATMAS03).

/DPe