Message type PRCMAS cannot be reduced

Hi friends,
Our company are running on multiple sap systems and now we want to process profit center master data on a single sap system and pass the data over to the other sap systems. I've found the standard message type PRCMAS which can realize profit center master data synchronization. But the issue is our controlling area is different between those SAP systems.
client
controlling area
100
1000
200
2000
300
3000
So, i must create a new reduced message type copy from PRCMAS. But the system pop-up a message:
Message type PRCMAS cannot be reduced
Message no. B1144
Diagnosis
There are different message types for different applications in the R/3 System. However, reduction is not possible for all message types depending on their business function and technical aspects.
Procedure
Please choose a message type that allows reduction
What should i do? I only want to set the conversion rule for the message type PRCMAS to set the controlling area as constant and assign to different client. But unfortunately, i cannot go ahead.
If someone could help me!
Thanks in advance
Jessie

For the message SERDAT processing in the inbound partner profiles should be set to 'immediate processing'.

Similar Messages

Reduced message type - Idoc without conversion rules

Hi Friends,
Am facing a strange situation while converting the Material Master data from 4.7b to ECC using BD21 transaction with reduced custom message type. I have reduced the standard msg type MATMAS05 using BD53 for the required field mapping both systems and I written the code using the exit EXIT_SAPLMV01_002 based on client req.
The situation is that sometimes IDocs are failing and the error shows that some fields which I have not selected in E1MARAM segment of the reduced msg type are populated with some values(ex: zeroes-0, slash-/,spaces)
Note: Conversion rules are not needed for this scenario.
Please help me out how to get rid of this '/ ' or spaces which appear for unselected fields in outbound Idoc using reduced message type ?
Thanks
Saravanan

Hi,
Please check the documentation in WE60 tcode and see if the fields are required to be passed...
Regards,
Nagaraj

FIDCCP01 Message type FIDCC2

Hello,
I am trying to use message type FIDCCP to create idocs for FI Document posting. However i am unable to see any idocs created. I have configured the system and activated change pointers for FI Documents. My question is does anybody have previous experience with FIDCCP message and change pointers and are idocs created using change pointers for FIDCC2. As when i run rbdmidoc and when i try to give FIDCC2 it says "message type fidcc2 cannot be sent via change pointers. Request you to help in this regards.
Regards,
Shekhar Kulkarni

Hello Shekhar,
you don't need change-pointers.
You must customize the ALE-Scenarion for FIDCC
Best Regards
Anton

Problem to create change pointer for custom message type - Idoc creation

Hi,
We want to create IDOC and send it out when the data of "planning calendar" changes. So we are trying to generate change pointers whenever entries in Table T439I (Planniing calendar) data change.
We created a message type, activated change pointers generally and maintained change relevant fields for message type (not sure if this step is done correctly). But not getting any change pointer in table BDCP2 when I create a new planning calendar in MD25.
Can anybody help / guide?

Thanks once again,
I had linked idoc type and message type in we82. Now after i activate the change pointers. I try to generate the IDOC type using BD21. It gives me the error message : "Message type ZP2PPROJ_MSG cannot be sent with change pointers"
whereas in my segments i am using all the master data only (i.e. PRPS, PROJ,PRHI). Please throw some light on this.
Also please clarify, do i need to make an entry of this custome message type in the partner profile ?
Rgds
kewal.

Change pointer for custom message type

Hi,
I have a situation where in, i need to create a custom message type and need to track the changes in the table fields using the Change pointer technique.
Can anybody guide me as to what are the step to be followed after i create the custom message type and how to register the fields of the message type ?
Note : Change document (CDPOS) technique is ruled out in my requirement.
Regards,
Kewal.

Thanks once again,
I had linked idoc type and message type in we82. Now after i activate the change pointers. I try to generate the IDOC type using BD21. It gives me the error message : "Message type ZP2PPROJ_MSG cannot be sent with change pointers"
whereas in my segments i am using all the master data only (i.e. PRPS, PROJ,PRHI). Please throw some light on this.
Also please clarify, do i need to make an entry of this custome message type in the partner profile ?
Rgds
kewal.

Had a recent crash on my macbook, was previously using OS 10.6 I think. Restored from recent Time Machine backup and updated to OS 10.8.2 and now I cannot open Logic Pro 9. I get a 'No entry' Icon and a not supported on this type of Mac message. I cannot

Had a recent crash on my macbook, was previously using OS 10.6 I think. Restored from recent Time Machine backup and updated to OS 10.8.2 and now I cannot open Logic Pro 9. I get a 'No entry' Icon and a not supported on this type of Mac message. I cannot update either as anything up to 9.1.1 tells me I don't need it yet 9.1.2 tells me I need an eligable Logic Pro Version was not found in applications.
All of my files are stored in a separate hard drive with only the actual app having been on my Macbook. Should I just reinstall?

Hi
To run Mouitain Lion you need to update Logic.
For the updaters to work the Logic application must be:
a) Within the Applications folder, and not in any sub-folder
b) Named "Logic Pro" with no extra numbers or spaces
CCT

Error Message: JBO-25009: Cannot create an object of type:oracle.jbo.domain

Hi, When im giving a default value to a date column in the attribute settings i get this error when im running my jsp page (bc4j web application):
Error Message: JBO-25009: Cannot create an object of type:oracle.jbo.domain.Date with value: 31-dic-2099
How can i fix that? I�ve already trying all possible date formats.
Thanku

The default format for Date (oracle.sql.DATE which is the superclass of oracle.jbo.domain.Date) is yyyy-mm-dd.

Issue with the change pointer for the reduced message type ZMATMAS

Hi All,
I have created reduced message type ZMATMAS for the MATMAS to create a Idoc when change or insert material master data fields( MARA-LAENG, MARA-BREIT, MARA-HOEHE) . My Problem is that the Idoc is generated with the status (03) but the fields(LAENG, BREIT,HOEHE) are not getting fill with the values. They are always filling with the values '/'). I have done the following steps to create idoc for the change pointer. Please check whether i have missed some steps.
1.     Create reduction maintenance ZMATMAS (Tcode BD53)
keep the default selected segments E1MARAM, E1MAKTM
2.     Add following data to maintain table view for the message type ZMATMAS (Tcode BD52)
Object      Table Name     Field Name
MATERIAL       MARA      KEY
MATERIAL     MARA     LAENG
MATERIAL     MARA     BREIT
MATERIAL     MARA     HOEHE
3.     Activate particular change pointer in BD50
Message Type       Active
ZMATMAS         yes
4.     Activate change pointers u2013 Generally (Tcode BD61).
5.     Assign Segment fields to change document fields (Tcode BD66 )
Segment Type     Field Name     Object     Table Name     Field Name
E1MARAM     BREIT     MATERIAL     MARA     BREIT
E1MARAM     HOEHE     MATERIAL     MARA     HOEHE
E1MARAM     LAENG     MATERIAL     MARA     LAENG
6. I have done the distribution model settings (BD64) and the idoc configurations
1.     Logical System
2.     RFC destination
3.     Create port
4.     Create partner profile
7. I changed the fields in material master data(Tcode MM02) and I executed the Tcode BD21.
Idoc is generated but the fields are not getting fill with the values
(Note: some fields are filled with values e. g material number, material description)
I checked the Idoc data segment E1MARAM (WE02)
Fld name   Fld cont.
LAENG       /
BREIT       /
HOEHE      /
Can you please let me know the issue
Prad

Issue is solved when I select the segments and the fields in the segments (Tcode :BD53)
Prad

What's the difference between segment filtering and reduced message type

Hi gurus,
What's the difference between segment filtering and reduced message type? It seems they have the same functionality: Reduce the segment while idoc is generated.
Thanks in advance.

Hi,
BD53 is for IDoc Reduction.
this allows you to create a reduced message based upon a standard message type.If you want see mandatory fields. go to T-coe BD53 and give one standard messege type name and eg: matmas
there mandatory fields will be in Green color..
And BD56- This transaction is used to filter out segments of IDocs for combination of sender and receiver. This is usefull in scenarios where a standard IDoc with many segments is used but the receiving partner is only interested in some of the segments
the table related to this transation is TBD20
please go through below blog you have an idea abt that,
http://wiki.sdn.sap.com/wiki/display/ABAP/ReducedMessageTypes
http://saptotal.com/IDoc%20Segment%20Filtering.html
regards,
ganesh.

JMS sender adapter : message type null is unknown, payload cannot be read

Hello,
We are building a scenario Weblogic -> PI through a JMS adapter, but we are getting the following error in the adapter :
2009-09-29 12:09:58 Information New JMS message with JMS message ID ID:P<450046.1254218997063.0> received. The XI message ID for this message is e705a65f-3cf6-472a-3675-b04e9862ce45.
2009-09-29 12:09:58 Warning JMS message ID:P<450046.1254218997063.0>: message type null is unknown, payload cannot be read and will be empty!
2009-09-29 12:09:58 Warning JMS message ID:P<450046.1254218997063.0>: Payload empty or cannot be read.
2009-09-29 12:09:58 Information JMS Message was converted to XI message succesfully.
Despite the fact that the message is not readable, PI creates a message anyway but the payload is empty. It is the same issue as described in this thread :
How to read Java Object message from JMS Queue using JMS Adapter .
But there have been no answer there.
We have read many notes but none are relevant, any ideas ????
Many thanks,
GL

Hallo,
Have you seen this note:
[Note 837501 - J2EE JMSAdapter: Empty payloads, unknown JMS message types|https://service.sap.com/sap/support/notes/837501]?
Seems it can be either message
a) does not contain any payload and/or
or
b) is not of type TextMessage or BytesMessage
/Jakub

Change pointer on reduced message (not standard-reducible message type)

Hello all,
I want to dedicate change pointers creation about classification.
CLFMAS idoc is not reducible in the standard.
With BD60, I modify the standard message type in order it to be reducible.
I can have created a reduced message type ZCLFMAS and I have activated change pointers on it.
When I modify a material classification, CLFMAS CP is created but not ZCLFMAS one.
Do you have a idea about the missing configuration ???
Thanks a lot

Hi,
>>>In this interface, we have to send only changed and newly created Employees to Legacy system. For this we are using change pointers which will capture all the changes.
No standard idoc is available which can suffice our requiremen; so we have created a custom IDoc and enabled change pointers on it.
what about HRMD_ABA ?
standard idoc for sending employees from SAP ?
everything is in standard with it
Regards,
Michal Krawczyk

How can I add an extention to a reduced message type?

We want to create change pointens for a subset of the HRMD messagetype.
So we created a reduced message type (based on HRMD_A07) and activated only those segment we need.
This works fine.
Now we need to add information of IT2006, this is not available in the HRMD. Therefore we made a Z segment and an extention to HRMD_A7. We added the extention to the partnerport and to the infotype (T777D).
The new segment is not send with PFAL, what do we need to do to make this work?

You need to make sure the new Z segments are populated with the data. You can check that by putting a break point in function module MASTER_IDOC_DISTRIBUTE and check the EDIDD parameter MASTER_IDOC_DATA. Check whether your Z segment is populated there. And check in parameter COMMUNICATION_IDOC, whether your extension is there. If your Z segment is not populated, you may have to check how that can be populated.
Regards,
Gokul

Reduced matmas message type data transfer to mdm

Hello ,
I have scenario where I have reduced matmas message type (Zervicematmas) and it is linked to matmas05.I want to transfer this data using mdm_clnt_extr.
Uptill now my understanding is that mdm_clnt_extr can transfer data for standarad
message type as(DEBMDM,MATMAS).
if yes , pl suggest what config has to be done on ECC6.0.
thanks in advance,
Sharada

Thanks for the help,
As per your suggestion one can select sengment to be transfered at the time of creating a variant of Extraction.
My scenario is that I have to create a custome message type ZSERVICEMATMAS for transferring data to MDM and standard MATMAS will be used to trnasfer data to other third party system.
Now here MDM_CLNT_EXTR is able to give me idoc wrt MATMAS message type and MATMAS05 idoc type.
I want MDM_CLNT_EXTR should create idoc for ZSERVICEMATMAS meesage type and MATMAS05 is idoc type.
I have checked for exits is MATERIAL_extract FM where I can give this message type, but didnt got any clue.
Pl can you suggest on this.
thanks,
Sharada

Need to ALE only 2 fields through a reduced message type copied from MATMAS

Hi,
Only the Authorization group fields MARA-BEGRU and MARC-QMATA need to be transferred through ALE from one system to another one. A new reduced message type has been created from MATMAS.
The fields BEGRU and QMATA have been selected through the BD53 transaction to be part of the segments.
Result: 3 segments are part of the new Message type: E1MARAM and its 2 children E1MAKTM and E1MARCM.
Problem: Even the BD53 (Reduced message type) transaction has been used, too many unnecessary fields are transferred through the ALE.
The following fields in the E1MARAM segment must not been updated (transferred) in the receiving system:
 - PSTAT,
 - LVORM
 - MTART
 - MBRSH,
 - MATKL,
 - MEINS,
 - GROES,
 - WRKST,
 - SPART,
 - VPSTA.
They should disappear from the segment.
The E1MAKTM segment must not been transferred to the receiving system because the user does not want to modifiy the Material description. But the BD53 (reduce message type) seems to consider that segment as mandatory.
Only few 1EMARCM segments with specific Plants (WERKS) should be sent on the receiving system. Not all the Plants. That segment should not include the PSTAT field. I have no control on which Plants to transfer.
Revision:
Only 2 segments must be ALE'd with only the following fields:
 1- E1MARAM:
 a) MATNR (Material number)
 b) BEGRU (Authorization group)
 2- E1MARCM:
 a) WERKS (Plant)
 b) QMATA (Material Authorization Group for Activities in QM).
What should I do to ALE only those 2 segments and only those specific fields?
Thanks a lot.
Diane.

Thanks Ferry for the previous answer,
I have a problem with the E1MARCM segment.
My sending and receiving systems do not have always the same Plant numbers.
If a Plant exists on the sending system and it does not on the receiving system, the Plant must not be created on the receiving system. But from the sending system, I do not know which Plants the receiving system has. This is why the IDoc contains all the Plants. But I added some logic in the inbound customer-function, EXIT_SAPLMV02_002, to ignore the Plants that do not exist on the receiving system in doing a SELECT on the MARC table in the receiving system.
But that customer-function is called from the IDOC_INPUT_MATMAS01 function module, in the " WHEN E1MARCM " section:
 PERFORM CHECK_USER_EXIT TABLES T_EDIDD
 USER_SEGMENTS
 USING CURRENT TABIX.
 LOOP AT USER_SEGMENTS.
 CALL CUSTOMER-FUNCTION '002'
 EXPORTING
 MESSAGE_TYPE = IDOC_CONTRL-MESTYP
 F_CUST_SEGMENT = USER_SEGMENTS
 ENDLOOP.
In the perform check_user_exit, no record is created in the user_segments table because all the segments in my IDoc start with ' E1 ' :
 LOOP AT IDOC_DATA INTO USER_SEGMENTS FROM CURRENT_TABIX.
 IF USER_SEGMENTS-SEGNAM(2) = ' E1 '.
 EXIT.
 ENDIF.
 APPEND USER_SEGMENTS.
 ENDLOOP.
The customer-function is called within the ' loop at user_segments '. This is why the customer-function is never executed and my code is ignored. So, all the IDocs in the receiving system are in the status 51 (red light).
Do you have any idea how to resolve my problem.
Thanks.
Diane.

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 PRCMAS cannot be reduced

Similar Messages

Maybe you are looking for