Está en la página 1de 14

Customer message wizard

Customer messages - DisplayHelp


Reporter
Name Gustavo Zuluaga

Company Empresas Juan Gass� Gass�, S.A.

Address Santo Domingo

Phone 1-809-537-3161

Fax DO 1-809-537-6048

Message
Number 002007974700001749592001

Status Confirmed

Installation data
System type Production system

Installation 0020062772 Instalaci�n T�cnica Santo Domingo

Release Release 4.0B

Add-on

System data
Oper. system NT\\\/INTEL4.0

Database MSSQLSRV7.0

Frontend WINDOWS 32

Classification
Priority Medium

Component MM-IM-GF-INC-Stock Inconsistencies

Description
Language Ingl�s

Short text Incorrect stock qty\\\\\\\/stock value in material


master
Long text
I\'m posting a goods issue to scrap from blocked stock in one of
the
storage locations. In that storage location, there are 5 pieces the
date I\'m trying to post the issue. However, the system allows me
to...

Notes
� 0032236 Incorrect stock qty\/stock value in material master
� 0076926 Check list f. material inconsistencies (value, qty)

Communication
02.10.2001 04:42:27 Dear Mr. Zuluaga,
Have you already imported the reports given in the note 32236?. If
not
please do so. Could you also please answer to the questions from the
checklist given in the note 76926?.

Thanks in advance for your cooperation.

Best Regards

Arminda Jack SAP Support

02.10.2001 11:48:43 Tratamos de importar los reportes dados en la


nota 32236, tratando de co
nectarnos al "sapserv4", pero no logramos accesar, el usuario que
tenemo
s para conecction OSS no funciona, debemos usar otro diferente...?

Gracias.

03.10.2001 06:25:50 Dear Mr. Zuluaga,

please try to import the reports from sapserv3 and let me know the
results.
Kind regards,

Nuria Cotelo, SAP Support

03.10.2001 09:00:03 Sra Cotelo.

Quisiera saber si es posible que se cambie el idioma del mensaje a


espa�
ol, porque no me manejo muy bien con el ingles y temo perder
informacion
importante en una mala traduccion.

Lo segundo es, que ya logramos conectarnos a SAPSERV4 pero


necesitamos s
aber cuales son especificamente los reportes de debemos bajar porque
en
la nota 32236 no lo especifica y hasta ahora estamos detenidos en
este p
aso.

Le agradecemos que nos den respuesta lo mas pronto posible, ya que


hace
tiempo que tenemos este problema y queremos ver la forma de
solucionarlo
a la mayor brevedad posible.

Gracias.

Rocio De Los Santos

03.10.2001 11:20:33 Sra.de los Santos,


la nota 32236 describe los pasos a seguir:

1) Comprobar que el report RM07MMFI est� presente en su sistema. Si


no
lo est�, implementarlo de acuerdo a la nota 198596.

2) Utilizando la transacci�n SE11, verificar la versi�n actual de


las
tablas MMINKON y MMINKON_UP. En la versi�n actual, el campo
CANCEL_YR
est� incluido en la tabla MMINKON_UP. Si estas tablas no existen, se
deben importar usando los siguientes transportes y activ�ndolas
despu�s:

Para la versi�n 4.x:


ALRK299728 en el directorio "general/R3server/abap/note.0032236"

Cuando se importen las tablas MMINKON y MMINKON_UP, los siguientes


elementos de datos deben estar activos:
BWTAR_D, CHARG_D, FELD_30, F_SPLIT, LFDNR_MM, LFYEAR, LGORT_D,
MMINKON_K, NEW_VALUE, NEW_VAL_C, OLD_VALUE, OLD_VAL_C, PROG_KEY,
TABN_30, VERS_MM, WERKS_D, XMBEW_FI, XMBEW_MM, XMSEG_MM

3) Importar el fichero:

ALRK303784 en el directorio 'general/R3server/abap/note.0032236'

Este archivo contiene los siguientes reports de chequeo:

MBFIRST, MBQUANT, MBVALUE, MBSTOCK, MBLABST, MBMISSFI, MBFIRST,


MBANEKBE, MBCKBSEG, MBENQMAT, MBGENKAL, RM07MR51, RM07MB51, MBTRAME,
RM07REUS, RM07APP1, MBSEGBSX, RM07AUTH, RM07UPLD, MBINKON, RM07COMP,
RM07HIST, MBUPDATE, MBSTART, MBHIST, MBCKMI1 y MBSHOWUP.

Un saludo,

Nuria Cotelo, SAP Support

A continuaci�n procedo a incluir la traducci�n de mi respuesta al


ingl�s, ya que el servicio de Soporte es un servicio internacional y
debemos trabajar en ingl�s para asegurar la atenci�n al cliente 24
horas.
*************************************************

TRANSLATION:

the note 32236 describes the steps to follow:

1. Report RM07MMFI must be present in your system. If it is not,


implement it as specified in Note 198596.

2. Using Transaction SE11, check whether the current version of


tables
MMINKON and MMINKON_UP exist. In the current version, field
CANCEL_YR
is present in table MMINKON_UP. If they do not exist, the table must
be imported using the following transports and then activated:
For Release 4.x:
ALRK299728 in directory "general/R3server/abap/note.0032236"

When you import tables MMINKON and MMINKON_UP, the following data
elements must be active:
BWTAR_D, CHARG_D, FELD_30, F_SPLIT, LFDNR_MM, LFYEAR, LGORT_D,
MMINKON_K, NEW_VALUE, NEW_VAL_C, OLD_VALUE, OLD_VAL_C, PROG_KEY,
TABN_30, VERS_MM, WERKS_D, XMBEW_FI, XMBEW_MM, XMSEG_MM

3. You must import command file

ALRK303784 in directory 'general/R3server/abap/note.0032236'

in your system. The command file contains the following check


reports:
MBFIRST, MBQUANT, MBVALUE, MBSTOCK, MBLABST, MBMISSFI, MBFIRST,
MBANEKBE, MBCKBSEG, MBENQMAT, MBGENKAL, RM07MR51, RM07MB51, MBTRAME,
RM07REUS, RM07APP1, MBSEGBSX, RM07AUTH, RM07UPLD, MBINKON, RM07COMP,
RM07HIST, MBUPDATE, MBSTART, MBHIST, MBCKMI1 and MBSHOWUP.

Regards.

04.10.2001 11:10:39 Hola

Ya tenemos todos los reportes necesarios, los bajamos al equipo de


desar
rollo.

Los objetos de las tablas MMINKON y MMINKON_UP se pueden activar


todos a
la vez, o debemos hacerlos uno por uno...?, si es uno por uno,
necesita
remos una clave de acceso para cada uno...?

Luego de activar las tablas, debemos transportar los reportes


indicados
al equipo de produccion.....? debemos nosotros hacer algun
procedimiento
con esos reportes....?

Anexo le envio las respuestas de la nota 76926

Gracias.

Rocio De Los Santos Acosta.

05.10.2001 09:24:37 Sra. De Los Santos,

Los elementos de datos de las tablas MMINKON y MMINKON_UP deben


activarse uno por uno:

BWTAR_D, CHARG_D, FELD_30, F_SPLIT, LFDNR_MM, LFYEAR, LGORT_D,


MMINKON_K, NEW_VALUE, NEW_VAL_C, OLD_VALUE, OLD_VAL_C, PROG_KEY,
TABN_30, VERS_MM, WERKS_D, XMBEW_FI, XMBEW_MM, XMSEG_MM

Los reports deben ser transportados al sistema productivo porque los


desarrolladores trabajar�n en el sistema productivo. Ustedes
solamente
tienen que cargarlos en el sistema productivo, sin ejecutar ninguno
de estos reports, y enviarnos de vuelta este mensaje.

Por favor, env�e en este mensaje las respuestas de la nota 76926


porque
de momento no es posible a�adir como attachement otro tipo de
documento
(Word,...) a los mensajes OSS.

Muchas gracias por su colaboraci�n.


Un saludo,

Nuria Cotelo, SAP Support


**************************************

Dear Mrs. De Los Santos,


the data elements of the tables MMINKON and MMINKON_UP must be
activated
one by one:

BWTAR_D, CHARG_D, FELD_30, F_SPLIT, LFDNR_MM, LFYEAR, LGORT_D,


MMINKON_K, NEW_VALUE, NEW_VAL_C, OLD_VALUE, OLD_VAL_C, PROG_KEY,
TABN_30, VERS_MM, WERKS_D, XMBEW_FI, XMBEW_MM, XMSEG_MM

The reports have to be transported to the productive system because


the
developers will work on the productive system. You only have to load
the reports on the productive system, without running none of them,
and send this message back.

Please send this message back with the answers to the note 76926
because at the moment it is not possible to attach another kind of
document (Word,...) to an OSS message.

Thanks for your cooperation.


Regards

05.10.2001 16:43:24 Ya tenemos todos los reportes en el sistema de


produccion, y le estoy en
viando la informacion requerida en la nota 76926, por favor aviseme
cual
quier cosa que necesiten.

Gracias.

Rocio De Los Santos Acosta.

************************************************************************
Customer check list for inconsistencies

************************************************************************
General information:
====================
1. Contact person at the customer for the application?
BERNARDO ARACENA
2. Contact person at the customer for the remote connection?
ALEJANDRO DE LA CRUZ
3. Data on the remote connection (only give us the IP address,
system, c
lient, user, password by telephone)?
PODEMOS ENVIARLES LA INFORMACION POR MAIL SI ES NECESARIO

Note that a consistency check is only executed in the productive


system,
in order that the inventory analysis considers all data and
documents.
4. Have you already imported the reports from Note 32236 (data
inconsist
encies) to your productive system in the current version (see Note
32236
)?
(If "NO", import them)
(If "YES", start Report MBFIRST and check the version specified in
the f
irst line of the list)
Reports from note 32236 Version: 00012
5. Have you already had data inconsistencies in your system in the
past?
NO
6. If "YES", specify the corresponding SAPnet-R/3 Frontend message
numbe
r. Which notes were implemented in response to your message then?
7. Do you use program SAPCKU1 (update of the prices in the material
mast
er record; Transaction CKU1)? If "Yes", refer to Note 154298.
NO TEMENOS ESE PROGRAMA

************************************************************************
Case 1: Differences between MM and FI (RM07MBST/MB5L). You cannot
specify an individual material.
1. Affected company code?
2. Affected plant(s)?
GS01
3. Affected balance sheet account and corresponding valuation class?
4. Have you already archived material documents?
NO
5. Have you already archived accounting documents?
NO
6. (As of Release 3.0)
Are you using the material ledger?
(Check with Transaction OMX1)
NO
7. With the workflow for report RM07MBST, check your system for
possible
application errors, for example, manual posting, incorrect account
dete
rmination, and so on.
If you have access to SAPNet, navigate to the specified web page as
desc
ribed in Note 175111 and answer the questions on the inconsistencies
tha
t have occured with "Yes".
Follow the instructions of the Analysis Assistant. Athough these
instruc
tions are part of the Support Guide for the Euro Conversion, they
are ge
nerally valid for the analysis of inconsistencies.
Specify the individual analysis results in your answer to the
checklist.

************************************************************************
Case 2: False or negative warehouse stocks with one (or several)
specified material for which no negative stocks are allowed
1. Affected company code?
2. Affected plant(s)?
3. Affected material number?
4. Is it a material with batch management?
5. Is it a material with split valuation?
6. Do you have already archived material documents? Have R/2
material do
cuments been migrated?
7. Do you have already archived accounting documents?
8. (As of Release 3.0)
Are you using the material ledger?
(check this with Transaction OMX1)
9. Do you have other materials in the affected plant with negative
wareh
ouse stock where they are not allowed?
(Check this using Transaction SE16, table MBEW, field LBKUM < 0)
10. When has a release upgrade been performed and from which R/3
release
?

08.10.2001 05:46:13 Sra. De Los Santos,

I have forwarded this issue to our next support level in Germany for
further investigation. Should you have any queries about this issue
in the mean time, please do not hesitate to contact us.
Best regards,

Nuria Cotelo, SAP Support

09.10.2001 08:38:46 Call to customer: Mr. Alejandro de la Cruz


Mrs. Rocio de los Santos
Telephone number: +1 809 537 3161
Subject:
- Confirm logon data (productive system):
system GG1, client 100, userid JGASSOSS, password 12345
- Material number with inconsistencies (example):
10255010
- Open the remote connection system GG1

09.10.2001 09:33:06 Hello Mr. Gustavo Zuluaga,

We have found the inconsistency reported on material 10255010 plant


GS01. We now need you to post a false posting of 1 piece to the
following location so that we may update your system. This posting
should be reversed after the update and when there is enough stock
to
allow this.
Please post one piece to :
material no. 1025501 Plant GS01 Storage location 0080 Batch L6V29A
MCHB-CSPEM = Blocked batched stock.

We also found an inconsistency on material 90018005 plant GS01 for


the
amount of 10,043.28. This was due to a unrecorded update to MBEW
between
01.12.2000 and the 12.01.2001. Have you archived materials for that
period or is there any explainable reason for this?

We can update for this and make your system consistent, but as it is
so long ago and not permanently recorded we cannot pinpoint the
reason.

Same with Material 90021025 plant GS01 doc no. 5000003711 which
failed
update MARD.

And also Material 90016031 plant GS01 which needs to be updated by 2


pieces in MARD, we will do this.

When you have completed the false posting, please open the
connection
and send this message back to me and we will attend to it asap.

Thanking you,

Sheila

09.10.2001 11:57:10 Hola

Ya tenemos una pza del material 10255010 en el stock bloqueado del


almac
en 0080 del lote L6V29A.

Tambien tenemos otro material con inconsistencia que es el material


6001
0005 de la planta IP01

Gracias.

Rocio.

_______________________________________

Hello

Already we have a piece of the material 10255010 in the Blocked


Storage
location 0080 of Batch L6V29A.

Also we have another material with inconsistence that isthe material


600
10005 of the plant IP01

Thanks
Rocio.

10.10.2001 10:51:14 Hello Rocio,

We have updated for the materials we discussed previously, your


system
is consistent for them.

We have checked the last material reported, Material 60010005 plant


PI01

This is the result of our report:

000000000060010005 IP01 0130 50189


MCHB-CLABS 57.000 1,383.000- 1,440.000-
Neg. stock not allowed for this field -> No update possible.
000000000060010005 IP01 0130
MARD-LABST 1,440.000 0.000 1,440.000-
Summary plant IP01: Found 2 errors in 1 materials.

Total: Found 2 errors in 1 materials.

Therefore you would need to post 1,383.000 to MCHB-CLABS for batch


50189...

We have checked your tables, MCHB has this exact amount in batch
10107.

If it is not meant to be there, you can do a goods movement between


the batches.

Please investigate this situation and whether this stock is in the


correct area. Also please indicate whether you have a stock level of
1,440.000 or 0 for this material in this plant as we cannot see any
failed postings.

We can update for this inconsistency but we need to reflect the true
situation with this material.

When you have completed the above, please return this message with
all
of the information available to me and we will then continue.

Thanking you,

Sheila

10.10.2001 11:46:04 Hola Sheila

Ya revise el material que tenia inconsistencia y ya esta bien, lo


que qu
iero saber es si debo reversar el movimiento que hice ayer, entre un
pi
eza al stock bloqueado con un movimiento 555, quiero saber si debo
rever
sar ese movimiento o si debo dejarlo, y si esto afectara alguna
cuenta.
con Respecto al otro material, no tenemos existencia del mismo, por
lo q
ue el stock deberia estar en cero.
Tenemos otro caso, y es con la actualizacion de ciertos materiales
en un
a estructura, la transaccion es la MC.9 y el programa es el
RMCB0300, el
caso es que algunos materiales no se actualiza en esta estructura
para
ponerle un caso especifico estos son los datos del material por la
trans
accion MC.9: Material Stock total Val.stk.valor. Total 3,640 PZA
409,372
.26 DOP 10375035 VENTOLIN SOLUCION RESP 10 ML 3,640 PZA 409,372.26
DOP P
or la transaccion MB52 tengo la siguiente informacion que es la
correcta
: Material Texto breve material Ce. Nombre 1 Alm. Util. libre UMB
Valor
total Mon. 000000000010375035 VENTOLIN SOLUCION RESP 10 ML GS01
Gass� Sa
nto Domingo W001 3,640 PZA 166,701.88 DOP pueden ustedes revisar
esto, o
tengo que abrir otro caso para esto...? Gracias. Rocio.

_______________________________________

Hello Sheila

I checked the material that had nconsistence and already this well,
wha
t I want toknow is if I have to reverse the movement that I did
yesterda
y, among a piece al stock blocked with a movement 555, I want to
know if
I owe reverse that movement or if should leave it, and if this
affected
some account.

With Respect the other material, we dont have existence of the same
one,
for which the stock should be in zero.

We have another case, and is with the actualizacion of certain


materials
in a structure, the transaction is the MC. 9 and the program is the
RMC
B0300, the case is that some materials is not brought up to date in
this
structure to put him a case I specify these are the data of the
materia
l by the transaction MC. 9:
Material Stock total Val. stk. value. Total 3,640 PZA 409,372.26 DOP
103
75035 VENTOLIN SOLUCION RESP 10 ML 3,640 PZA 409,372.26 DOP
By the transaction MB52 I have the following one informacion that is
the
correct one:

Material material brief Text Ce. Name 1 Alm. Util. free UMB total
Value
Mon. 000000000010375035 VENTOLIN SOLUCION RESP 10 ML GS01 Gass� Holy
Sun
day W001 3,640 PZA 166,701.88 DOP

You are able you to analyze this, or I have to open another case for
thi
s. ..?

Thanks. Rocio

10.10.2001 13:22:01 Hello Rocio,

Yes you will have to reverse the false posting you made when there
is enough material available to do so.

So you have no stock of material 60010005, is this correct? If you


wish us to update for it, please tell us.

For the last matter, I am afraid I cannot deal with it, you will
have to open another OSS message for it.

The connection has cancelled now, I will contact you to open it


tomorrow.

Thanking you,

Sheila

10.10.2001 13:58:55 Hola Sheila

No tenemos stock del material 6001005, por favor, actualicenlo.

Entiendo que tendre que reversar la falsa entrada que hice del
material
pero cuando lo haga, tendre una pieza faltante en el stock, como
resolve
re esa situacion.

Gracias

Rocio.
______________________________________

Hello Sheila

We have no stock o material 60010005, please update it.

I understand that will have tom reverse the false posting thatI did
of t
he material but when do it then I will have a missing piece of the
stock
, how I will resolve that situation...?

Thanks.

Rocio.

11.10.2001 08:57:30 Hi Ricio,

I need you to post a movement to move the stock for material 6001000
plant IP01 from batch 10107 to batch 50189.

When this is done, please open the connections and send this back to
me

You will not have one piece of missing stock when you reverse the
false
posting. You had one extra piece of false stock before the update as
a movement to -1 from your stock failed. So your stock will be
correct.

If you wish you can do a physical count to check this. If there is


a difference between your physical stock and your system stock,
please
follow the instructions below to reconcile them. If you need to,
please
do this after you have reversed the false posting.

Procedure to reconcile physical/actual stocks:

1: Using transaction MI01 you generate a document number, please


take a
note of this number.

2: Then using transaction MI04 enter the physical amount, you will
need
the document number for reference here.

3: Use transaction MI07 with the document number again, this will
auto
post the difference.

Thanking you,

Sheila

11.10.2001 09:23:41 Hello Sheila

I already post a movement to move the stock for material 60010005


plant
IP01 from batch 10107 to batch 50189.

Thanks.

Rocio.

11.10.2001 09:49:36 Hello Rocio,


We have updated your system. It is consistent now. If you wish to
view
any of the changes we made to your system, please run report
MBShowup
or view table MMINKON_UP.

When you have checked your system, please confirm this message so
that
we can remove it from our lists.

If you have any other queries, please do not hesitate to contact me.

Thanking you and wishing you every success,

Sheila

11.10.2001 10:11:53 Hello Sheila

The Material (10255010)that was blocked in the stock was there to do


a W
ithdrawal for scrapping from blocked stock (movement 555), but we
could
not do it due to system inconsistencies. If I reverse the input
movement
I made, then I will not have materials in the blocked stock and
therefo
re I will not be able to to the Withdrawal for scrapping. Thats why
I as
ked you if I will have a missing piece in my stock after de
reversalmove
ment.

Thanks.

Rocio.

11.10.2001 10:50:52 Hello Ricio,

I understand your situation. But the inconsistency was that, one of


the
material movements failed to remove 1 piece from batch L6V29A.

But there was no stock in the batch record. As other postings had
removed all of it.

That was why you had to falsely post 1 piece in.

I then updated both MARD and MCHB, removing 1 piece from each to
balance
your system with your material documents.

So it left MCHB with 0 and MARD with 1 piece. We advise you to


reverse
the false posting as your physical stock will now, not match your
system
stock, that is why I recommended you to do a stock check.
You do not have to reverse immediately, you can reverse when there
is
enough stock there through normal business postings.

It is your business decision how you reconcile your physical stock


with
your system stock.

If everything else is okay, please confirm this message.

Thanking you,

Sheila
Attachments
04.10.2001 11:08:50 ANSWER NOTE 76926 ANSWER NOTE
76926.doc

También podría gustarte