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

Similar Messages

Received unexpected message type does not match expected type

1.Two Biztalk Applications A,B one for sending the request(A) and other application will send the response to A.
2.I have two schema Request and Response in Aplication A which i have exposed as webservice.
3. Application B share the same response schema .
I am using WSBasicHTTP sysnchronous ports to send and receive the message.
WHen Application B send the response , i get the error "unexpected message type does not match expected type "
but i dont know why i get such error when the schemas are share by both application. Please advice
Regards
Suresh

Hi Suresh,
Whenever you are doing request-response like calling web service etc, i would suggest to use Passthrough pipeline while sending and use XML receive for receiving the message.
Because when you are sending the message out it doesn't needs any promoted properties so you can use Passthrough this will avoid extra Assembling/Validation etc tasks performed by XMLSend pipeline.
But when you are receiving response that time it expects MessageType property to be promoted because normally you will have receive shape configured to some Typed Schema. So you will have to use XML Receive pipeline.
Thanks,
Prashant
Please mark this post accordingly if it answers your query or is helpful.

SAProuter error message server hostname not defined

Dear all,
I am trying to install SAP router for my system i have done the basic installation but i check my sap router using
lgtst u2013H /H/198.168.201.157//H/194.39.131.34/S/sapdp99/H/oss001/S/sapmsO01 u2013S x u2013W 30000
it gives an error message:
* can't connect to message server
* reason : message server hostname not defined
can someone help mw with solution.
Regards,
Gaurav sood

Dear all,
Will you please check SAPROUTTAB setting
as i am getting error message as
C:\>lgtst -H /H/192.168.201.157/S/sapdp99/H/172.29.4.168/S/sapdp99/H/oss001/S/sa
pmsO01 -S x -W 30000
using trcfile: dev_lg
[Thr 2416]
[Thr 2416] * LOCATION    SAProuter 38.10 on 'transporter'
[Thr 2416] * ERROR       transporter: route permission denied (TRANSPORTER to
*              172.29.4.168, sapdp99)
[Thr 2416] *
* TIME        Fri Jun 11 12:34:45 2010
[Thr 2416] * RELEASE     700
[Thr 2416] * COMPONENT   NI (network interface)
[Thr 2416] * VERSION     38
[Thr 2416] * RC          -94
[Thr 2416] * COUNTER     3
[Thr 2416] *
[Thr 2416] *****************************************************************************
SAPROUTTAB file
# SNC connection to SAP
# SNC-connection from SAP to local R/3-System for Support
KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" * *
KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 194.39.131.34 *
# SNC-connection from SAP to DVP system for R/3 Support & SAPTelnet
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 172.29.4.168 3200
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 172.29.4.168 23
# Access from your local Network to SAPNet - R/3 Frontend
P * sapserv2 3299
P * 147.204.2.5 3299
# All other connections will be denied
D * * *
Regards,
Gaurav Sood

Activate change point for message type - message type FIDCC1 not in list

I want to set up idoc for sending entire FI documents.
For this I want to use the change points in the message type FIDCC1 but this message type is not in the list of transaction BD50 (neither if I go via SALE)
I'm not allowed to add it myself, I get a warning the name is not in the namespace (Zxxx or Yxxx).
Is there a way I can add this message type in this list?
-> change points are generally activated
-> ECC 600
edit: I see the message type is in WD81
Edited by: Renaat Vanhaverbeke on Apr 28, 2010 11:05 AM

I found the solution: when I tried to add the message type in BD50 I got the warning the name does not match the namespace rules. But by opening the Performance Assistant I could start the transacion RDDKOR54 to display the namespace rules.
By exiting this transaction I got the question if I want to bypass the namespace check and by answering positive on this I could save the new entry.
PS: I also found that alle message types are defined in table EDMSG

Erroe Message: Type Expected

I need some help. I am getting the error message Type Expected with this line of code
System.out.print("Your commission is $" + CommissionAmt);
Any suggestions would be welcomed.

Here is the complete code with 2 errors. one, type expected and one, semicolon expected.
public class Commission               //start of class
     public static void main (String[] args)     // method declaration
(ERROR2)          double Sales=$5000.25;                          //variable
          int CommissionRate=1;                         //variable
          double CommissionRate.07;                    //variable
     //declare and define an object CommissionAmt
     Commission CommissionAmt = new Commission ();
(ERROR 1)     System.out.print("Your commission is $" + CommissionAmt);     //print
     } //closes the main method
} //closes the class

IDOC message type WMMBXY not including Serial numbers in GR material documents when created with reference to an Inbound delivery

Hello,
We currently have an inbound ALE process (message type WMMBXY and basic type WMMBID02) to post GR's against inbound delivery. If the inbound delivery item is maintained with serial numbers, we want those serial numbers to be pulled into the goods movement material document (and stored in SER03).
Currently segment E1MBXYJ is maintained with the inbound delivery number in field VLIEF_AVIS and Inbound delivery item number in field
VBELP_AVIS. In segment E1MBXYI, no purchase order is assigned and the fields EBELN and EBELP are blank. The movement indicator (KZBEW) has the value 'B'.
Even after making the above settings, the serial number(s) maintained on the Inbound delivery item do not get saved to the material document.I did look at OSS note 833603 (Solution for 2 - GR for Inbound delivery) and we have followed the same settings. This works when there is no serial number in the Inbound delivery. However if we have serial numbers, the IDOC posts successfully, however the material documents in MB03 do not have any serial numbers copied over from the Inbound delivery where the serial numbers are definitely assigned.
Any help you can provide is greatly appreciated!
Thanks,
Ashvin
P.S
If we manually create the GR via MIGO, the serial numbers are automatically applied to the GR material document. This is what we want to accomplish via the above IDoc process.

Hi
Try with enhancement MWMIDO08. See note 833603 - EDI: Goods receipt for stock transport order for further information.
I hope this helps you
Regards
Eduardo

Message 'Entry is not defined in table T706U'

Hi folks.
System gives this message when adding entry to trip:
'Entry is not defined in table T706U'
DUMP: Overflow during the arithmetical operation (type P) in program "RPRTEC00".
1205 * split
1206       ELSE.
>>>>         UEB-ANZAL = UEB-DATB1 - UEB-DATV1.
Program values:
UEB-ANZAL 3
UEB-DATB1     00010102 <---- Error
UEB-DATV1     20110801
Any tip ?
thanks.
Glauco
Edited by: Glauco Kubrusly on Jun 27, 2011 12:27 PM
Edited by: Glauco Kubrusly on Jun 28, 2011 1:51 PM

Unflag meal option in SPRO and TRIP/PR05.

Output Message Type MAHN not getting picked up in PO

Hello Experts
   I have configured customized output type ZMAH (similar to MAHN) for reminder process. When I am creating PO this output type is not getting picked up automatically. If I am maintaining it manually I am able to send message for ME9F (Purchase Order) and ME91F (Reminder) successfully. Upon deremination analysis I am getting this message 502 " Output ignored (requirement 103 not fulfilled) ". Reminder are getting picked up from Purchase Value Key to PO.
Any help is appreciated.
Thanks
Ankit

Hello Tej
I have maintained output device but same result.
Here I am listing all parameters that I have used for configuration can anyone please take a look and let me know if I am missing anything
Steps for new Message Type for PO Reminder (ZMAH)
1.     Defined new Table 026 Purchasing Output Determination: Document Type
                                                    (ii) 027 Purchasing Output Determination: Purch. Org./Vendor for EDI
2.     Defined new access sequence Z515 Access Sequence for Archiving.
Following are parameters to the Access Sequence
Access Sequence Number = 1
Table = 026
Description = Purchasing Output Determination: Document Type
Requirement = 103
Exclusive = Yes (box checked)
Access Sequence Number = 2
Table = 027
Description = Purchasing Output Determination: Purch. Org./Vendor for EDI
Requirement = 103
Exclusive = Yes (box checked)
3.     Maintain Output Type ZMAH for PO
General Data
Access Sequence = Z515
Access to condition (Checked)
Multiple Issuing (Checked)
Change Output
Program = SAPFM06P
FORM Routine = ENTRY_NEU
Replacement of Text Symbol
Program = SAPMM06E
FORM Routine = TEXT_SYMBOL_REPLACE
Default Values
Dispatch Time = Send Immediately (when saving application)
Transmission Medium = External Send
Communication Strategy = 0001 (E-mail Document)
Processing Routines
Transmission Medium = 5 (External Send)
Program = SAPFM06P
Form Routine = ENTRY_NEU
Form = MEDRUCK
Partner Roles
Medium = External Send
Funct = VN
Name = Vendor
4.     Fine-Tuned Control: Purchase Order
Oprat. = 3
CType = ZMAH
Name = Output for Reminder
Short Text = Urging letter (expediter)/reminder
Update Print Related Data = Yes (checked)
5.     Maintain Message Determination Schema: Purchase Order
Procedure RMBEF1 (Purchase Order)
Step = 101
Cntr = 3
CTyp = ZMAH
Description = Output for Reminder
Requirement = 103
6.     Assign Schema to Purchase Order
Procedure RMBEF1
7.     Define Partner Roles for Purchase Order
Out. = ZMAH
Med = 5 (External Send)
Funct = VN
Name = Output for Reminder
Name = Vendor
8.     Test Condition Maintained in MN04 (Master Data)
Purch. Org. = 0001
Vendor = 101281
Partner Funct = VN
Medium = 5 (External Send)
Date/Time = 4 Send immediately (when saving application)
Output Device = LP01
Cover Page Text = Reminder PO number &EKKO-EBELN&
Also I have configured Purchasing Value Key, reminders are coming to PO correctly.
Thanks
Ankit

URGENT! Idoc Message Type FIDCC2 Not Posting CO Documents

Hi Everyone,
Our company is just about to begin using message type FIDCC2 to post entries through FB60/FB65 and FB50. When you manually enter an entry through any of these transactions, an FI, CCA and PCA document are all created simultaneously. However, when posting an identical entry through message type FIDCC2, only an FI document is created. Why are the other documents not being created and is there something that I am missing from configuration or some sort of trigger that is supposed to create the other entries? Please assist as this is extremely urgent.
Thanks to all that can assist,
Pete

Hi Peter,
Is your company uses any of the profitability segment fields as well? If so how are you updating this information on to the FIDCC2 idoc and how are you generating any COPA document simultaneously. I am in the same situation and my FIDCC2 idoc updates the FI, CO, PCA components but not the COPA. I am not sure where to populae the Profitability segments on the FIDCC2 type. Please share if you have same issues in your company.
Regards
Elphick

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

Idoc Message Type FIDCC2 Not Posting CO Documents

Hi Everyone,
Our company is just about to begin using message type FIDCC2 to post entries through FB60/FB65 and FB50. When you manually enter an entry through any of these transactions, an FI, CCA and PCA document are all created simultaneously. However, when posting an identical entry through message type FIDCC2, only an FI document is created. Why are the other documents not being created and is there something that I am missing from configuration or some sort of trigger that is supposed to create the other entries? Please assist as this is extremely urgent.
Thanks to all that can assist,
Pete

Hi Peter,
Is your company uses any of the profitability segment fields as well? If so how are you updating this information on to the FIDCC2 idoc and how are you generating any COPA document simultaneously. I am in the same situation and my FIDCC2 idoc updates the FI, CO, PCA components but not the COPA. I am not sure where to populae the Profitability segments on the FIDCC2 type. Please share if you have same issues in your company.
Regards
Elphick

Message type is not triggered in SAP when PO copied from eSHOP

Hi,
We are creating PO in eShop and sending to SAP.
POs are correctly getting copied from eShop to SAP.No issues.
We have set condition record for Message type to trigger in SAP for those POs as EDI Medium.
No message is getting triggering in SAP.
Whether it is standard one ? or any further enhancement required ? If so please suggest the BAPI.
Thanks

Hi Dhina
What is the application eSHOP?.
for example
In SAP SRM - Technical scenario - Extended Classic.
Purchase orders were created in SRM -EBP and replica of Purchase Orders were replicated to ECC system. In the above scenario messages are created in SRM not ECC.
The PO messages are out puted to vendor from SRM itself.
So please clarify what is meant by eShop. so others can help you further ..
Muthu

IDOC message type LOIPLO not triggering

Hi Friends
Our client want to send firmed planned orders to External system through outbound IDOC LOIPLO
So we are using MF50 to firm the planned orders.
The idoc message type LOIPLO is not triggering.
How to trigger IDOC message type LOIPLO . What are the settings we have to do.
Regards,
Srihari.M

dear friend,
Message Type : LOIPLO
Basic Type : LOIPLO01
You need not create any custom IDOC type as we are having a standard IDOC type available within SAP, but you need to write a custom function module to read the data from the IDOC segments and then call the below BAPI to post the Planned Order.
Check the input parameters of BAPI and gothrough the documentation of the Basic Type in WE60 transactions, whether all the necessary input parameters of the BAPI are covered in the standard IDOC type, if not then we need to customize the standard basic type to meet the requirements.
Bapi which needs to be used is BAPI_PLANNEDORDER_CREATE
good luck!

Message type to be defined plantwise

Hi,
We have defined a message type to post PO from MM to SRM(SUS).The message type currently is vendorwise , we need to make it plantwise.
Please advise.
Thanks in Advance,
Manu

Can you use addition DISPLAY LIKE dtype. Dtype is "A", "E", "I", "S" or "W" in upper-case letters.
If you use another letter the message don't show the icon.
Example:
Message I305 DISPLAY LIKE 'N'.
The message is without icon but when display show the letter N like this:
N:Message
Regards
Angelo.

Distibution Model- Outbound parameters for message type could not be found

Hi SRM Gurus,
Have you ever encountered this error while buidling Distribution model in BD64 -
When I try to generate partner profile, I am getting this error-
Outbound parameters for message type BBPCO BBPCO01 could not be created
Partner not found in partner table
This error is occuring for all message types.
Please let me know the solution if anyone has encountered this error before.
Thanks & Regards
Kapil

Hi
Are you geting this error while generate partner profile?
hope your sender and receiver logical system are correct.double check.
VERSION 3
OUTPUT MODE - tRANSFER idoc immediately option
connectivity between both sytems are ok.
did you save modelview ?
now ports automatically created . check we21 ,we20..
check your sm59 rfc destination? what type connection you made ? hope you maynot do mistake. howevercheck itup.
ask basis consultant assistance why ports anot genrated for backend system after you executed
tbd05 - do yo have entry ?
regards
muthu

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

Similar Messages

Maybe you are looking for