Message type 'X' dump in ISU_REFVALUE_FACTS_UPDATE

Hi All,
Requirement: Transfer data from a .CSV file to table ETTIFB using ISU_REFVALUE_FACTS_UPDATE.
Issue: In case there is an erroneous data combination of data or data mismatching with the datatype of field in ETTIFB , ISU_REFVALUE_FACTS_UPDATE goes to dump.
SAP : 6.20.
I tried searching notes but have not got any for 6.20 release.
Is there any way I can handle this programatically (exception handling etc.)
My design: I have made a custom program which calls this FM ISU_REFVALUE_FACTS_UPDATE to update ETTIFB.
Thanks,
Rajesh

Similar Messages

Message type 'X' dump in BAPI_CATIMESHEETMGR_INSERT

Hi All,
Requirement: Transfer data from a Z table to CATSDB using BAPI_CATIMESHEETMGR_INSERT.
Issue: In case there is an erroneous data combination of data or data mismatching with the datatype of field in CATSDB , BAPI_CATIMESHEETMGR_INSERT goes to dump.
SAP : 6.20.
I tried searching notes but have not got any for 6.20 release.
Is there any way I can handle this programatically (exception handling etc.)
My design: I have made a custom method which calls this BAPI to update CATSDB.
Thanks,
Regards,
Kumud Singh

Hi Rajesh,
I found out that CATS was dumping because the data provided was erroneous. I found this dump at the initial stages of development. If you pass the right combination of data, you would not face this issue. Moreover, it is easy to debug and find that exact place which causes the dump.
On the other side, I also realize that it should not dump rather throw some error message. There are no SAP notes that I could find to resolve this issue. You could also do a search on available SAP notes.
Thanks.
Regards,
Kumud

RFC dump : 'Message type " " is unknown.'

Hi everyone,
I am calling an RFC from one system to another and i am getting a dump with error :
Message type " " is unknown.
When i debugged the program the found that nothing is returned for " MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4. "
What should i do to rectify the problems? Please do help.
Thanks In Advance.
Regards,
Heera

ABAP runtime errors    MESSAGE_TYPE_UNKNOWN
       Occurred on     03/05/2008 at 21:56:28
Message type " " is unknown.
What happened?
The current ABAP/4 program "Y_MM_C_CICS_MAT_RECON " h
because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 progra
What can you do?
Print out the error message (using the "Print" functi
and make a note of the actions and input that caused
error.
To resolve the problem, contact your
SAP system administrator.
You can print this message by choosing "Print".
Transaction ST22 allows you to display and manage sho
is especially useful if you want to keep a particular
Error analysis
Only message types A, E, I, W, S and X are allowed.
How to correct the error
If the error is in one of your own ABAP programs or an SAP program that
you have modified, try to correct it.
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
"MESSAGE_TYPE_UNKNOWN"
"Y_MM_C_CICS_MAT_RECON " bzw. "Y_MM_C_CICS_MAT_RECON "
"START-OF-SELECTION"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.
3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.
System environment
SAP Release.............. "46B"
Application server....... "fmsap591"
Network address.......... "10.19.196.114"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "2x IA64 Level 3"
Database server.......... "FMSAP591"
Database type............ "ORACLE"
Database name............ "AI0"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "46D"
Created on............... "Jul 30 2007 00:11:29"
Created in............... "NT 5.0 2195 Service Pack 2 x8
Database version......... "OCI_920_SHARE__OCI_7_API "
Patch level.............. "2335"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.0.5.., ORACLE 8.0.
8.1.6.., ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE 1
SAP database version..... "46D"
Operating system......... "Windows NT 4.0, Windows NT 5.
Windows NT 5.2, , System build information:,
                                      , LCHN : 921411"
User, transaction...
Client.............. 250
User................ "HPRAMANX"
Language key........ "E"
Transaction......... "SE38 "
Program............. "Y_MM_C_CICS_MAT_RECON "
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where termination occurred
The termination occurred in the ABAP/4 program "Y_MM_C_CICS_MAT_RECON " in
"START-OF-SELECTION".
The main program was "Y_MM_C_CICS_MAT_RECON ".
The termination occurred in line 371
of the source code of program "Y_MM_C_CICS_MAT_RECON " (when calling the editor
3710).
Source code extract
003410       r_lgort-sign = 'I'.
003420       r_lgort-option = 'EQ'.
003430       r_lgort-low = x_storeloc_wa-ecc_st_locn.
003440       APPEND r_lgort.
003450     ENDLOOP.
003460
003470
003480   *CALL RFC TO GET MATERIAL DATA FROM F PIPE BY PASSING S_MATNR r_werks
003490   *r_lgort S_CHARG AND GETTING THE REQUIRED DATA BACK IN THE TABLE
003500   *I_MCHBF
003510
003520     CALL FUNCTION 'YCICS_MATERIALDATA'
003530     DESTINATION 'FI0250'
003540          TABLES
003550               i_matnr                        = s_matnr
003560               i_werks                        = r_werks
003570               i_lgort                        = r_lgort
003580               i_charg                        = s_charg
003590               i_mchb                         = i_mchbf
003600          EXCEPTIONS
003610               no_data_found                  = 1
003620               material_not_of_type_fert      = 2
003630               invalid_plant_entry            = 3
003640               invalid_stloc_entry            = 4
003650               invalid_plnt_matnr_combi       = 5
003660               invalid_plnt_matnr_batch_combi = 6
003670               invalid_plnt_matnr_batch_stloc = 7
003680               OTHERS                         = 8.
003690     IF sy-subrc <> 0.
003700    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
     >            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
003720     ENDIF.
003730
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 1                             SY-INDEX 0
SY-TABIX 1                             SY-DBCNT 31
SY-FDPOS 0                             SY-LSIND 0
SY-PAGNO 0                             SY-LINNO 1
SY-COLNO 1
Chosen variables
Name.......................... Contents.1........2........3....+....4
VARI
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 40                                          ####00000000000000
                               2222222222222222222200003333333333333322
                               0000000000000000000000000000000000000000
... + 80                          ####################################
                               2222000000000000000000000000000000000000
                               0000000000000000000000000000000000000000
... + 120                      ########################################
                               00000000
                               0000000
SY-MSGV1
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 40
                               2222222222
                               0000000000
SY-MSGV2
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 40
                               2222222222
                              0000000000
Y-MSGV3
                              2222222222222222222222222222222222222222
                              0000000000000000000000000000000000000000
.. + 40
                              2222222222
                              0000000000
Y-MSGV4
                              2222222222222222222222222222222222222222
                              0000000000000000000000000000000000000000
.. + 40
                              2222222222
                              0000000000
_MCHB                         #######################################
                              0000000000000000000000000000900000009000
                              0000000000000000000000004000060000001000
.. + 40                      ####0###0#######ÿÿÿÿ:###########è ####
                              1000300030000000FFFF300000000000EA280000
                              0000020001000000FFFFA000200043008D030000
.. + 80                      x> ####################################
                              7328000000000000000000000000000000000000
                              8E03000000000000000000000000000000000000
.. + 120                      ########################(#######
                              00000000
                              0000000
MCHBWA                      000000000000895405CR01CRA10001    CR01TE
                              3333333333333333334533454333332222453354
                              0000000000008954053201321100010000320145
.. + 40                      ST05####e#########
                              553300006000000000
                              3405000150C000000C
SCHARG_%_APP_%              S_CHARG S_CHARG                       to
                              5544454255444542222222222222222222222276
                              3F3812703F38127000000000000000000000004F
.. + 40
                              2222222222222222222222222222222222222222
                              0000000000000000000000000000000000000000
.. + 80                         @1FQMultiple selection@
                              2224345547676766276666766642222222222222
                              000016C1D5C490C5035C5349FE00000000000000
.. + 120
                               222
                               000
X_MCHBF_WA
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 40                      00000000            00000000
                               3333333322222222222233333333222222222222
                               0000000000000000000000000000000000000000
... + 80                      000000 #################################
                               3333332000000000000000000000000000000000
                               0000000000000C000000C000000C000000C00000
... + 120                      ########################################
                               00000000
                               0C00000
I_MCHBF                        ################@#######################
                               0000000000000000400000000000100000000000
                               1000400040004000080050004000080000000000
... + 40                      ################ÿÿÿÿÓ###################
                               1000000000000000FFFFD0000000000000000000
                               0000000000000000FFFF30007000630000000000
... + 80                      ########################################
                               0000000000000000000000000000000000000000
                               0000000000000000000000000000000000000000
... + 120                      ########################8#######
                               00000000
                               0000000
SYST                           ########################################
                               0000000000000000000000000000000000000000
                               0000000010000000000000000000000000000000
... + 40                      ####################ã###################
                               10000000000000000000E0000000000000000000
                               F00000001000000010003000000000000000F000
... + 80                      ########################################
                               0000000000000000000000000000000000000000
                               0000000000001000800000000000000000000000
... + 120                      #######################################
                               00000000
                               0000000
X_MKPFMSEG_WA-BKTXT
                               2222222222222222222222222
                               0000000000000000000000000
%_SPACE
                               0
                               0
X_OUTPUT_WA-BTEXT
                               22222222222222222222
                               00000000000000000000
X_MCHB_WA-MATNR                000000000000895405
                               333333333333333333
                               000000000000895405
X_MKPFMSEG_WA-WERKS
                               2222
                               0000
X_MCHB_WA-WERKSF               CRA1
                               4543
                               3211
X_OUTPUT_WA-WERKS
                               2222
                               0000
X_MCHB_WA-LGORTF
                               2222
                               0000
X_MKPFMSEG_WA-LGORT
                               2222
                               0000
X_MCHB_WA-CHARG                CR01TEST05
                               4533545533
                               3201453405
Active calls / events
No.... Type........ Name..........................
       Programm
       Include                                  Line
     1 EVENT        START-OF-SELECTION
       Y_MM_C_CICS_MAT_RECON
       Y_MM_C_CICS_MAT_RECON                      371
Internal notes
The termination occurred in the function "ab_jmess" of the SAP
Basis System, specifically in line 1083 of the module
"//bas/46D/src/krn/runt/abdynpro.c#22".
The internal operation just processed is "MESS".
The internal session was started at 20080305215621.
Active calls in SAP kernel
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
Callstack without Exception:
App       : disp+work.EXE (pid=24072)
When      : 3/5/2008 21:56:28.0
Threads   : 2
Computer Name       : FMSAP591
User Name           : ai0adm
Number of Processors: 2
Processor Type: ia64 Family 31 Model 1 Stepping 5
Windows Version     : 5.2 Current Build: 3790
Stack Dump for Thread Id 56f4
FramePtr         ReturnAd         Param#1          Function Name
00000000083a0c00 0000000076eab530 00000000000024f4 kernel32!GetDateFormatW
00000000083a0bd8 000000000215a7c0 00000000000024f4 kernel32!GetDateFormatW
00000000083a0b88 000000000067fe80 0000000000000080 disp+work!
000000001c1b0040 0000000076ea7420 0000000000212e50 MSVCRT!tanhf
000000001c1b0000 0000000000000000 000006fb7eb36e88 kernel32!GetDateFormatW

Updates rules activation triggers dump message type X

Hi,
In an existing update rule, I am trying to add a field (key figure=> characteristic (source)
after I activated the update rules a shot dump is triggered
"Message type X"
message class RSAA
Number 108
trigger location
%_T005N1
Module Name Instantiate
called function :
RSAU_GET_CUBE_TIME
I have already done some consistency test about the infocube in RSRV, but don't dind a clue for the moment.
any help would be grateful
John

Hi
Try to run standard program RSAU_UPDR_REACTIVATE_ALL.
Thanks
lokeshM

Error while trying to post inbound idoc of message type COND_A

Hi,
I am getting error while trying to post inbound idoc of message type COND_A.
If I left Usage & Condition field of segment E1KOMG then 'Table not available' idoc message is coming
and if providing value in above fields then dump is coming.
How to solve ?
Plz do reply
Thanks
Mohit

I do not see any reason why you would need to use COND_A04 if COND_A01 is working.
What if you could get COND_A04 to post and you would face the same result as in COND_A01?
If SAP does not check wrong values, then you have to do it yourself, or you report an incident at SAP (after you have searched for OSS notes that may have fixed this error already)
For example OSS Note 1169998 - IDoc: KONP-LIFNR values not checked
fixed a situation where the vendor number was not validated.

Message type is not populating in the Inbound idoc control record

Hi,
I have created an Inbound Idoc function module and have done the necessary Idoc settings. But, while testing in WE19, I observed that control record is not getting populated with message type and it is dumping.
The settings which I have done in WEDI as follows:
1. Created Idoc segments with necessary fields and released
2. Created Idoc type for the segment type
3. Created message type
4. Assigned message type to basic type
5. In the inbound processing settings,
filled the ALE attributes with the Idoc function module name and input value '0'
6. Assigned FM to basic type and message type
7. Created process code and assigned the process code to message type
Please let me know, the reason for the message type not populating in the control record. Useful answers will be surely rewarded.
Best Regards,
Mallika

Hi,
Maintain partner profile (Transaction code WE20) for the message type you defined in WE81 and put your process code in partner profile and check your logical system settings also in transaction SALE.
Thanks
Rahul

Fault message types: Why do we need them?

Hi guys,
I have a bpm scenario created, tested and working.
This bpm starts with a async receive, a Sync Send to a R3 system by an ABAP proxy and a final async send to the original system.
I'm contemplating exception handling and other type of errors. Meaning, if the abap proxy dumps I can raise an exception and map it on the XI environment. The thing is, on sxmb_moni I get the exception handler, with the exception texts, id's, etc... from the R3 being mapped to the XI fault message type.
But the problem is I can't get to map the text from the fault message type into any field from the response of the original system.
I've searched the forum and I've seen that this area is surrounded by doubts and questions...
But in the end I'm forced to place the question, why do I need the fault message types? What use can I give them, besides of the cute little thunder on the sxmb_moni?
Thanks for your attention guys

Hi Krishna,
I've read the SAP description about Fault Message Types but I'm still struggling on how to use them correctly.
Why do we need them if I can't do nothing with it on the BPM side? After the mapping of the FMT, I'd like to acess it so that I can send a description back to the original system...The thing is, in BPM you can't acess the FMT, you can only create a new BRANCH (on a block step) for it...
I've tried to acess the description text on trace which comes with the message, but it seems that the trace only serves for posting info, and not for getting any...
The Mapping Runtime Constants have some information where you can read some descriptions, but nothing related to the errors....You can read the Receiver service, sender, interface_namespace, but nothing from the ERROR tag...
Is there a way to get the description? Or anything related to the error tag?
Thanks in advance

Message types?

hi am new to BI
pls help me to know about message types.
plese provide docs or pdfs if u have and that would be really helpful
thank u

Hi Ranjith,
Message Types:
A --> Termination Message
The message appears in a dialog box, and the program terminates. When the user has confirmed the message, control returns to the next-highest area menu.
E --> Error Message
Depending on the program context, an error dialog appears or the program terminates.
I --> Information
The message appears in a dialog box. Once the user has confirmed the message, the program continues immediately after the MESSAGE statement.
S --> Status Message and Sucess message
The program continues normally after the MESSAGE statement, and the message is displayed in the status bar of the next screen.
W --> Warning
Depending on the program context, an error dialog appears or the program terminates.
X --> Exit
No message is displayed, and the program terminates with a short dump. Program terminations with a short dump normally only occur when a runtime error occurs. Message type X allows you to force a program termination. The short dump contains the message ID.
For more info:
http://help.sap.com/saphelp_nw04/helpdata/en/2d/c0633c3a892251e10000000a114084/frameset.htm
Regards,
KK.

SolMan configuration - Message type "e" is unknown

Hi all,
every time i select the step 6.6 (Connect Diagnostics Agents to Solution Manager) of the System Preparation in SolMan 7.1 SP11 i receive the following message (and related dump in ST22).
Message type "e" is unknown.
Same thing happens in two different Solution Manager (same version and SPS).
Looking for SAP Notes without help.
Any suggestions?
Regards.

Hello guys,
We have a similar issue.
Here is why we got to this error. When i setup the SLD in step 6.1 i used another system, and the Solution Manager was non existent in that SLD/LMDB.
I now configured a local SLD in 6.1 and created a local LMDB.
I am now running the synchronization again ( which as you know takes a while ).
Probably the easiest way would have been just to define the system in the first LMDB, but in our case it's a development system and i wanted to try this also.
I will let you know after the sync is finished.
Catalin

What are message types ?

Hi..
I want to know the exact difference between message type and IDOC type.
I would be glad if anyone will explain me the function of Message type both technically and functionally.
One more thing which I would like to know is the main function of a Process Code . What exactly are they and what is its usage again both technically and functionally.?
Thanks in advance.

Message Processing
Message processing depends on the message type specified in the MESSAGE statement, and the program context in which the statement occurs.
Message Types
A
Termination
The message appears in a dialog box, and the program terminates. When the user has confirmed the message, control returns to the next-highest area menu.
E
Error
Depending on the program context, an error dialog appears or the program terminates.
I
Information
The message appears in a dialog box. Once the user has confirmed the message, the program continues immediately after the MESSAGE statement.
S
Status
The program continues normally after the MESSAGE statement, and the message is displayed in the status bar of the next screen.
W
Warning
Depending on the program context, an error dialog appears or the program terminates.
X
Exit
No message is displayed, and the program terminates with a short dump. Program terminations with a short dump normally only occur when a runtime error occurs. Message type X allows you to force a program termination. The short dump contains the message ID.
and idoc types are....:-
The IDoc types relevant to the distribution of article master data are as follows:
ARTMAS03
Pure article master data
INFREC01
Purchasing info records
SRCLST01
Purchasing source list
LIKOND01
Listing conditions
LAYMOD01
Layout modules
COND_A01
Sales prices and sales price conditions, and purchasing info record conditions
DOLMAS01
Document assignment
WTADDI01
Additionals
BOMMAT03
Bill of material (BOM) structure for components of structured articles and empties BOMs
Only one empties BOM per article can be distributed with this IDoc type. If an article has more than one empties BOM, the empties BOM that was created first is distributed.
The following empties BOMs have been defined for the full product lemonade:
Unit of measure
Empties
Order of creation
C12
1 large empty crate and 12 empty bottles
First
C6
1 small empty crate and 6 empty bottles
Second
PC
1 empty bottle
Third
The empties BOM for the unit of measure C12 is distributed; that is, it is the empties BOM with the number 1.
Unlike maintenance in online mode, it is not possible to create or change listing conditions or sales prices when transferring article data. Listing conditions and sales prices must be transferred in separate IDocs.
Although articles can be assigned to layout modules in dialog maintenance, these assignments are not distributed by the IDoc ARTMAS03 in outbound processing. The IDoc LAYMOD01 must be used to distribute them. For reasons of upward compatibility, the IDoc ARTMAS03 can still be used to process layout module assignments on the inbound side. When transferring data from a legacy system, you are recommended using IDoc LAYMOD01 and not IDoc ARTMAS03.
Please reward points.

Message type X Infopackage

Hi,
We copied our R3 PRD to TST and linked the BW Dev to TST.
I ran some of the process chain, one of process chain was 'DELTA' uplaod for 0GLACCOUNT. The the request failed.
Now when i try to go into the info package it dumps with Message type X message.
I read various message on this, however, my case is different. I do not see any delta que in RSA7 in R/3 source system for GL account and i cannot even open up or create a new infopackage in BW for me to create a Delta que in RSA7.
How do i resolve this ? Any ideas ?
Umang

Hi,
Refer note
Note # 852443 and 405943.
Read also Notes 591382 and 424848
Refer
Error - RSM1_CHECK_FOR_DELTAUPD
Short Dump when opening Info Package
Delete Initialization request
This should solve your problem.
Thanks,
JituK

NW2004s ABAP Trial Version Message Type X

Hie
I have installed NW2004s ABAP Trial Version but immediately after log on the system dumps with message type X, any transaction i try to execute dumps with that error. I am not even able to do ST22 it dumps as well!! Is there an installation step i missed out on??
regards
Isaac Prince

Hi Prince,
What else have you tried? Normally, you will get this message when you use an outdated version of the SAPGUI or if the system load did not complete correctly. Have you tried restarting the system?
Another place to check are the work process traces under the work directory. One of the dev_w# files should tell you if you are running into memory issues.
Hope that helps!
J. Haynes

Inutilização de NFe: Log de erro Message type 8 is not defined

Olá Pessoal,
Estamos com um erro aqui muito semelhante ao descrito na Thread: [Skip número da NF não autorizada|;.
Solicitamos a inutilização de uma nota writer de saída que foi barrada no Monitor GRC por erro de validação e por isso estava com status 8 na J1BNFE (ECC). A inutilização foi feita com sucesso, o status no GRC está correto, mas no ECC a autorização ainda não constava. Executamos o report XNFE/UPDATE_ERP_STATUS_DIAL e ao fazermos a msg de "erro ao atuzalizar ECC". No monitor da J1BNFE a nota agora aparece com o seguinte log de erro:
Message type 8 is not defined
Message no. J1B_NFE018
Diagnosis
The messaging system passed a value for the message type to the back-end system (field I_MSGTYP) that is not defined in the back-end system.
System Response
The back-end system cannot interpret and process the inbound message.
Procedure
Configure the messaging system in a way that it transfers only allowed message types to the back-end system via the inbound interfaces J_1B_NFE_XML_IN or J_1B_NFE_XML_IN_TAB.
Achei a thread mencionada acima com o mesmo erro e verifiquei a aplicação das notas, já que o problema foi solucionado com a aplicação das mesmas. Eis os status:
Nota 1298283 (ECC) - Não relevante pois estamos no ECC 6.0 SP17;
Nota 1376324 (ECC) - Não relevante pois estamos no ECC 6.0 SP17;
Nota 1413636 (ECC) - Completely Implemented na SNOTE;
Nota 1376901 (GRC) - Não relevante pois estamos no GRC SP13.
Aparenmente alguma coisa ainda está faltando.. mas nao sei o que é.
Desde já agradeço,
Daniela Machado

Verifique esses passos da nota 1298283 (no ECC)::
Change Domain J_1BNFE_MESSAGE_TYPE
Use transaction SE11
Select Domain and insert name J_1BNFE_MESSAGE_TYPE
Push Change.
Select Tab "Value Range".
Insert
Fix value Short text
8 Authorization to Skip a NF-e with Validation Error
9 Rejection to Skip a NF-e with Validation Error
Maintain table J_1BNFE_MAP_TYPE
Use transaction SE16 and display the table entries.
Push CREATE (F5)
Insert records
MSGTYP DOCSTA SCSSAT
8 Space A
9 Space B
At.,
Bernardo Braga
Edited by: Bernardo Braga on Jul 1, 2010 10:06 PM

Message type BOMMAT (change BOM)

Hello Guru,
I have some question and need help, when i try a standard transaction CS02, try to change a BOM material existing for example, the base quantity of the BOM was 650, i enter new data as 655, but suddenly retain the original Qty as 650 and save the changes as SAP will accept the changes i've done (BOM for material 2456 changed) but eventual i have not change any value to the original BOM. SO it mean this is standard SAP funtionality for CS02.
But when we use an interface using message type BOMMAT a standard SAP message tpye, we have created an IDOC using this message type and same data as the original was maintain to it, to be more exact we plan to change a BOM thru this IDOC but all the data we have is the same value of the original BOM, so we expect no error could be encounter of this IDOC since in standard CS02, changing of BOM even same value was inidicated did not had error message encountered when saving.
But thru our process, when we try to process the IDOC with message type BOMMAT in program RBDAPP01 (BD20) the idoc did not pass it when into status 51(Error when saving BOM. Please see the application log.) and when we check the BOM it has duplicate value upon executing the program we able to fix it when we delete the duplicate line segment in the IDOC and reprocess it once again.
my question is why in standard message type BOMMAT had encountered error when processing when we try to make change of BOM even the same value is carried out by the IDOC, and why in standard CS02 saving a change of BOm with same value as it is SAP accept the process? Please help and clear the process.
Any inputs R.Brahamankar and Vivek
Thanks
Edited by: Ryan on Feb 9, 2009 9:23 AM

BOMMAT and process code BOMM

Idoc and message type not getting replicated in the receiver system

Hi
i have created a Z Idoc and didtributed the mode from system A ....I can see the distribution model in system B
However i cannot see the custom zidoc / message type in sys B.. Do i need to create the zidoc again in sys B

Hi Tarang,
at least ou need the required partner agreements and you should have a processing function for inbound IDoc. To implement this, the full definition of IDoc including Segment definition should be present in receiving system.
Just look at standard IDocs and do as they do.
Regards,
Clemens

Message type 'X' dump in ISU_REFVALUE_FACTS_UPDATE

Similar Messages

Maybe you are looking for