Problem in SXMB_MONI

Hi Experts,
I have problem in SXMB_MONI when i am sending messages from RWB the messages which have BPM Associated with it are not been visible in SXMB_MONI but the messages which do not involve BPM that which are sent from RWB are visible .
what could be the problem its import for UAT
Thanks
Sampath

Hi...
The transaction that configures this options is sxmb_adm...
Did you try this?
Best regards.

Similar Messages

Can not see messages in SXMB_MONI of ECC

Hi Friends,
 Here I am facing some problem with SXMB_MONI of ECC. I am doing an XI upgrade from XI3.0 to PI 7.1.
when I am doing my interface upgrade I am unable to see messages in SXMB_MONI of ECC. As ECC is also got upgraded now BASIS is very confused about configuration.
 when I went through some blogs I came across some suggestions like configuration in SXMB_ADM. In ECC the integration engine configuration what I did is
 Role of Business System : Application System.
 Corresponding Integ. Server : dest://<HTTP DEST>
 One of my doubts:: Is <HTTP DEST> is the one which we are giving in XI/PI or the new one created for ECC. First BASIS set up <HTTP DEST> as the same one which was configured in PI. Then I went back to BASIS and tell them that ECC is having its own local Integration Engine, so we need to create <HTTP DEST> which connects to integration engine of ECC.
 Then they created one <HTTP DEST> for ECC. but when I am doing connection test, Http response is coming as 400 BAD HTTP Response :: protocol error. I have no idea why it is behaving like that.
 After when I go through some more blogs they are dealing with RFC destinations LCRSAPRFC and SAPSLDAPI. when I check it in ECC I didn't found RFC destination LCRSAPRFC but SAPSLDAPI is existing in ECC.
 more over some blogs deal with the configuration in Transaction SLDAPICUST. when I check it in ECC no configuration was done in SLDAPICUST.
 I already configured ENGINE_TYPE, IS_URL, LOGGING, LOGGING_PROPAGATION, LOGGING_SYNC under specific configuration data of SXMB_ADM of ECC.
 Please let me know what needs to be done and let me out of this confusion. As I am a PI developer I am unaware of all these configurations. expecting replies from gurus....
Regards,
DASARI

Hi Friends,
 Looking at some more blogs I got a doubt.
 Actually my scenario is File - XI - RFC.
 Now my doubt is whether we can see the messages which were going to ECC by RFC adapter ?
 Looking at a thread I got confused whether SXMB_MONI can capture messages only if they are coming from Proxy or IDOC . please clarify me.
Regards,
Dasari.

ABAP runtime error in sxmb_moni when SOAP message has header with some tags

Hi!!!
I have a problem with sxmb_moni transaction.
If I double-click on a successfully processed
message, then this monitor can't show me
the message details but fails with the following error:
<COPY_AND_PASTE_FROM_SCREEN>
Runtime errors OBJECTS_OBJREF_NOT_ASSIGNED_NO
Exception CX_SY_REF_IS_INITIAL
Occurred on 02.03.2005 at 16:44:21
Access with 'ZERO' object reference not possible.
What happened?
Error in ABAP application program.
The current ABAP program "CL_XMS_PROP_STRING============CP " had to be
terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
</COPY_AND_PASTE_FROM_SCREEN>
This situation takes place only when I want
to look at a SOAP message which was sent to XI
from .Net platform or was sent to
.Net platform from XI (via SOAP adapter).
In all other cases sxmb_moni works fine.
I know that the problem is connected with some tags from Header record of SOAP message:
 <soap:Header>
 <wsa:Action>http://aaa.bbb.ccc/MessageResponse</wsa:Action>
 <wsa:MessageID>uuid:1838f870-1688-4cfe-8c4f-afe14d98c515</wsa:MessageID>
 <wsa:RelatesTo>uuid:308b950f-8cff-4b63-9861-93b041825f9d</wsa:RelatesTo>
 <wsa:To>http://schemas.xmlsoap.org/ws/2004/03/addressing/role/anonymous</wsa:To>
 <wsse:Security>
 <wsu:Timestamp wsu:Id="Timestamp-389847df-8760-4d57-9777-6ce159d85205">
 <wsu:Created>2005-03-02T08:54:29Z</wsu:Created>
 <wsu:Expires>2005-03-02T08:59:29Z</wsu:Expires>
 </wsu:Timestamp>
 </wsse:Security>
 </soap:Header>
If I take a SOAP message I have problem with, and
I remove all tags from this Header (or remove
the whole Header) and send it from any XML editor
that can send SOAP messages then sxmb_moni hasn't
any problems with showing me details of a such message.
Any hints how to force a .Net platform not to send
a such header or how to force sxmb_moni transaction
not to fail if a such header occurs?
Regards,
Andrzej Filusz

Hi Santhosh
1.Check your authorization settings in XI and R/3. Whether the user has sufficient rights to execute the Function Module etc. This is the most common reason for this error.
2.If the XI system was brought online even before the R/3 system then re-activate the communication channels from the Integration directory.
Cheers..
Vasu
** Reward Points if found useful **

Queue stopped in sxmb_moni

Hi,
I am getting the problem in sxmb_moni when the XML message goes from one integration process to SOAP adapter and a mapping is called.The queue status is Queue Stopped. When i click on that queue it shows status as SYSFAIL.When i double click on that queue again it shows Status Text
as "XI Error CLIENT_SEND_FAIL . INTERNAL :Queue Stoppe ".
And the trace for that message is
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>
<SAP:P1>35</SAP:P1>
<SAP:P2>HTTPIO_ERROR_CUSTOM_MYSAPSSO-Fehlermeldung beim Senden der Daten.</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while sending by HTTP (error code: 35, error text: HTTPIO_ERROR_CUSTOM_MYSAPSSO-Fehlermeldung beim Senden der Daten.)</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Please help me with this issue...

Queue Stopped
For your message processing in sxmb_moni...in the Qstatus column you will be seeing a red circle with stop written in it...
->double click it
->it will show you status of the Q....number of messages in the Q...
-> double-click on the number of entries
-> you will see a detailed report
-> double click on the first entry
-> you will see the message processing due to which the Q got blocked
-> on the toolbar above (in the same page) you will find the option of Restart...click it....select the tracing level as retain....
this will cause the message processing to restart and all the messages blocked in the Q will get processed....
Regards,
Abhishek.

SXMB_MONI -- Runtime Table

Hi,
In SXMB_MONI --> Inbound -> SOAP Header --> RunTime I can see this values below (HOST is most interesting).
I have problems debugging (SXMB_MONI) in order to see which table(s) data is stored.
<SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Host>sappi03</SAP:Host>
Any one knows which table to look in ?
Br
Martin
Edited by: Martin Andersson on Jun 17, 2008 2:42 AM
Edited by: Martin Andersson on Jun 17, 2008 5:34 AM

Hi Martin,
Here are some tables.
SXMS_AE_AUDITCNF____________XI: Adapter Runtime Data
SXMS_AS_STATUS__________________Status Table of Synchronous/Asynchronous Bridge
SXMS_MULTIM_REF__________________Link-Table Leading Message - SubMessages
SXMS_PACKCOUNT__________________Counter for Packed Messages
SXMS_QUEUE_PRIO__________________Prioritized EOIO Queues
SXMS_SYSPAR__________________SAP System Parameter and Storage Location
SXMSAEADPMOD__________________XI: Adapter and Module Information
SXMSAEADPMODCHN____________XI: Adapter Module Chains
SXMSAEAGG________________________XI: Adapter Runtime Data (Aggregated)
SXMSAERAW________________________XI: Adapter Runtime Data (Raw Data)
SXMSALERTCNTRL____________ Control Table for XI Alerts
SXMSALERTCONTROL____________Control Table
SXMSALERTLOG__________________XI Alert Log
SXMSALERTLOGGER____________XI Alert Logs
SXMSALERTRULES__________________Rules for Alert Generation: Msg Header ->Alert Category
SXMSALERTSTEPS__________________PMI Process Steps for Alerting
SXMSALERTTMSTMP____________Time Stamp of Last PMI Process Instance Chhecked
SXMSARCITF________________________XML Message Archiving
SXMSCLUP________________________XMB: Property Cluster
SXMSCLUP2________________________XMB: Property Cluster (Switch Table)
SXMSCLUR________________________XMB: Resources Cluster
SXMSCLUR2________________________XMB: Resources Cluster (Switch Table)
SXMSCONFDF__________________XMS: Integration Engine Configuration Para
SXMSCONFVL__________________XMS: Integration Engine Configuration Data
SXMSDCONF________________________Integration Engine: Settings for Deletion
SXMSEPCACHE__________________XI: Runtime Cache for Exchange Profile
SXMSEPCLOG__________________XI: Log Table for Runtime Cache for Exchange Profile
SXMSFTEST________________________Table for XI Runtime Engine Test
SXMSGLOBAL__________________Integration Engine: Obsolete
SXMSHELP________________________Help Assistant
SXMSHELPT________________________Help Assistant (Short Text)
SXMSINTERFACE__________________Sender/Receiver Definition
SXMSINTF________________________XMB: Container for Application Monitoring(Template)
SXMSINTFT________________________Sender/Receiver Interfaces
SXMSITF________________________Search Help for Interface for Archiving (Without Content)
SXMSJINFO________________________Integration Engine: Job Information
SXMSJOBS________________________Jobs for Time-Controlled Message Processin
SXMSMONSEL__________________Selection Table for Integ. Engine Application Monitoring
SXMSMONSET__________________Selection Table for Integ. Engine Application Monitoring
SXMSMSGDEF__________________Message Definition
SXMSMSGFILLED__________________Message for a Message Definition Saved
SXMSMSGFILTER__________________SAP XI: Filter for Sender/Receiver Attributes
SXMSMSGINDCUS__________________SAP XI: Configuration Indexing of Messages
SXMSMSGINDLOG__________________SAP XI: Message Indexing Log
SXMSMSGINDSRV__________________SAP XI: Services for Indexing Messages
SXMSMSGPMI__________________Using XI Messages in PMI
SXMSMSGREF__________________Message Reference Storage
SXMSMSTAT________________________Exchange Infrastructure: Message Status
SXMSMSTATT__________________Exchange Infrastructure: Message Status Description
SXMSPADM________________________XMS Pipeline: Execution Settings
SXMSPCONF________________________XMB: Administrative Data for Pipeline Conf
SXMSPEMAS________________________Integration Engine: Enhanced Message Queue(Master)
SXMSPEMAS2__________________Integration Engine: Extended Message Queue(Switch Table)
SXMSPENTRY__________________XMS: Map Inbound Pipelines to XMB Pipeline
SXMSPERFC________________________SXMS: Runtime Measurement Results
SXMSPERFCD__________________SXMS: Data Table for Online Performance Data
SXMSPERFCH__________________SXMS: Header Table for Online Performance Data
SXMSPERFT________________________XMS: Monitor Table for Runtime Measurement
SXMSPERRO2________________________XMB: Message Queue (Entries with Errors) (Switch Table)
SXMSPERROR__________________XML Message Broker: Message Queue (Incorrect Entries)
SXMSPFADDRESS__________________Integration Engine: Sender and Receiver Information
SXMSPFAGG________________________Integration Engine: Aggregated Data for Performance Display
SXMSPFCOMPONENT____________Integration Engine: Component Information
SXMSPFMSGTYPEDB____________XMB: Selektionsdaten für Monitoring
SXMSPFRAWD__________________Integration Engine: Data Table for Raw Data for Performance
SXMSPFRAWH__________________Integn Eng: Header Table for Raw Data for Performance Evaln
SXMSPFSEARCHDB__________________XMB: Selektionsdaten für Monitoring
SXMSPHIST________________________XML Message Broker: History
SXMSPHIST2________________________XML Message Broker: History (Switch Table)
SXMSPIPE________________________XML Message Server: Pipeline Definition
SXMSPIPEEL________________________Pipeline Element Definition
SXMSPIPET________________________XMS: Pipeline Description
SXMSPLELT________________________XMS: Description of Pipeline Elements
SXMSPLSRV________________________XMS: Pipeline Service Specification
SXMSPLSRVT________________________XMS: Description of Pipeline Services
SXMSPMAST________________________Integration Engine: Message Queue (Master)
SXMSPMAST2__________________XML Message Broker: Message Queue (Master)
SXMSPMIRAW__________________Integration Engine: Performance Data Extracted from PMI
SXMSPTRACE__________________HTTP Trace
SXMSPVERS________________________Integration Engine: Message Version
SXMSPVERS2________________________Integration Engine: Message Version (Switch Table)
SXMSQUEUE_RCV__________________Mapping Queue Receiver
SXMSQUEUE_REORG____________Storage Location for Queues That Are Being Reorganized
SXMSQUEUESTATUS____________Queue Status During Upgrade Phase
SXMSRECVT________________________Technical Receiver
SXMSRTDIAG__________________Entries for Support Diagnostics
SXMSSPDIAG________________________Objects for SXMS SUPPORT DIAGNOSTICS
SXMSSPDIAGS__________________Objects for SXMS SUPPORT DIAGNOSTICS
SXMSSYERR________________________XMS: System Error Error Codes
SXMSSYERRT________________________XMS: Brief Description of System Error Codes
SXMSTRANS_CONFIG____________Configuration Table for Message Transfer
SXMSTRANS_HEADER____________Lookup Table for Message Transfer
SXMSTRANS_MSG__________________Body Table for Message Transfer
SXMSTRC_DAT__________________XMS: Trace Data
SXMSTRC_SEL__________________XMS: Selection Criteria for Trace Start
SXMSTSACT________________________Action Table for Integration Server Troublshooting
SXMSTSTRIG________________________Table of Troubleshooting Trigger
Best Regards,
Nagesh Y R
Edited by: Nagesh Rudhra Yellapu on Jun 17, 2008 1:43 PM

Failed process not in SXMB_MONI_BPE list

Hi,
I'm on Pi7.1 and have a BPM monitoring related problem: In SXMB_MONI I can see, that my process was aborted due to a faild send action (target system not reachable). When I invoke SXMB_MONI_BPE the process instance is not contained in the list of failed processes. Analyzing the BPM inbound processing queue (SQM2) I can find a stuck queue exposing the error messages "Permanent error in BPE inbound processing".
Does anybody have an idea, why the related business process is not contained in the list of faild processes in SXMB_MONI_BPE? - this was the case on XI3.0 -
Kind regards,
Heiko

Hi Heiko,
Check the OSS note 1126656 - BPE-TS: Permanent errors in the BPE inbound processing
In parrallel goto TCODE "SWF_XI_CUSTOMIZING".
Check whether ,any errors are there.
All entries related workflow or integration process should be with out any errors and active.
Regards,

Proxy Monitoring

Hi ,
I have the problem with Proxy.Let me exaplain my scenario and Problem.
Scenario: I am sending Idoc->Proxy
Problem: In SXMB_MONI, All the messages are showing with successful flag but my client is telling that some of them are not delivered. How can i monitor the Proxy whether it has the problem or it also delivered sccessfully. where can i do this??
Like File Adapter, we can check the status of it at Receiver CC in CC monitoring Right. In the same way How can i can i check the Proxy Monitoring at Reciver side??
Warm Regards,
Vijay
Message was edited by:
Gangisetty Vijaya Bhaskarudu

Hi,
Check SXMB_MONI in Application system not in XI since Proxies are adapter less.
Regards,
S.RamNarender

JDBC Receiver Synchronous SELECT With Proxy

Hi People,
We are trying a JDBC Receiver Synchronous select scenario, based on <a href="/people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step Kantilal's Blog</a>. Our scenario is somewhat different in the sense that we are using synchronous message interface as outbound, using this for proxy generation and then calling the EXECUTE_SYNCHRONOUS method to pass the values to Integration Server and get the response back. We are writing the response obtained. but the problem is, SXMB_MONI is showing no entry in the response message structure, although the SELECT query should select at least one record. Can anybody please point out where the error is residing? Is it an error of the JDBC Synch. Select, or do we have to use BPM in this case, as pointed by Bhavesh in his blog?
Awaiting your views,
Regards,
Amitabha

Hi People,
Thanks for all those hints...but We have solved the problem...there was an error in Response Mapping...So the corresponding import structure in EXECUTE_SYNCHRONOUS was not getting populated.
Awarded points for making us aware of the possible pitfalls in this scenario.
Thanks and Regards,
Amitabha

Bad Quality of Service for a new customer

I am very disappointed in my experience today.

Many thanks guys for professional Input!
My question based on following problem:
At SXMB_MONI all PO messages succssfully processed but no messages deliverd to the Vendor.
After deeper checks i detected following:
At Component Monitoring I see the respective Communication Channel in yellow with description "Channel started but inactive". So far as i know ... that means ... no messages was processed up to now!
At Message Monitoring i found a lot of PO Messages in Status "To Be Deliverd".
The last entry at Audit Log sounds "The message was successfully retrieved form the queue".
Message restart doesn't work! So i thought on message blocks the whole Adapter queue.
Do you have any solution for me?
Many thanks in advance!
Regards,
Jochen

Problem in processed XML in SXMB_MONI?

Hi,
SOAP -> XI -> File is my scenario
Processed XML is not getting displayed in SXMB_MONI.
In case if there is any error i get an error message in Monitor.
What is the procedure to capture the Successful message..
Thanks,
RPN
Edited by: RPN on Aug 30, 2008 11:55 AM

thanks hemanth,
My Scenario is SOAP --> XI --> FILE
I've created all the necessary objects in Integration repository and completed all the configurations in Integration directory.
I've created a web service for this scenario and loaded it into XML Spy, as am using this to send the SOAP Request
As this is an asynchronous process.. i think its assumed that if i didn't get a response.. the request has been completed.
But i don't see an messages in XI (SXMB_MONI), either the file created.
can you help me on this
Thanks,
RPN
Edited by: RPN on Aug 30, 2008 12:12 PM
Edited by: RPN on Aug 30, 2008 12:30 PM

Problem with scheduled message in SXMB_MONI

Hi All,
I have come accross an issue. There is a scheduled message in SXMB_MONI(with green flag). It's been there at for a long time.I can see a inbound queue name in the SXMB_MONI display. But if I am looking into the que from SMQ2, there is no pending messages in the queue. How to process this message? Can we reprocess it?
Thanks

Hi,
prerequisite:
make sure the message will not be processed in SXMB_MONI
a) restart the message from sender system
b) take the payload from SXMB_MONI and post it from RWB
directly to integration engine
test it on DEV to be sure what you're doing of course
Regards,
michal

Problem in transaction "sxmb_moni"

Hi,
when I sent a message from R/3 to XI I get following error that is shwon in transaction "sxmb_moni".
<<Error when reading from the secure store: ERROR_UN: No service user password found <<for Adapter Engine
Can anybody help me please??
Thanks.
Regards
Stefan

hi,
secure store is a java based service so try checking
the VA logs
as shown in my weblog:
/people/michal.krawczyk2/blog/2005/09/07/xi-why-dont-start-searching-for-all-errors-from-one-place
if there's any more infor to your error over there
(maybe the user name etc)
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Fault message in Asynchronous messages - SXMB_MONI in PI problem

Hello,
I am working on File to Proxy asynchrnous interfaces. I am using fault message type on inbound message interfaces.
I have done all the configuration according to below link
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
After raising the exception, I can see messages are being failed in ECC , but in PI moni, message status is successfully status.
I want PI message status "Application Error".
Any idea.
Thanks in advance.

Just letting you know fault message is not something message could not be processed or due to system error mesg failed or so.
Using fault message to show business errors for the application. Example if the request message does not have purchase order number, then fault mesg could be "Purchase order is missing". In this case, Pi will respond with fault message. But this is successful processing end to end.
Basically you get response from ECC as fault message not wrong in it. SO PI will show only success log.
Dont confuse messages failing due to system downtime or network issues or firewall issue with application or business logic errors. Hope that helps.

IDOC-XI scenario problem

I have a IDOC - XI scenario,
where IDOC is generating from a R/3,
the problem is, an IDOC was sent from R/3, but has not reached XI,
in R/3, i have seen in WE05, there i see this IDOC having status '03',
and, also in SM58, there i no error corresponding to this IDOC,
but in XI, in IDX5, i cant see that IDOC,
where the problem lies?

Make sure that the sender partner and receiver partner values corrrespond to the logical system names you have used in your partner profile in we20. Sender Partner Name should be your R3's logical system name, and Receiver Partnr Name should be the Logical System name for which you have created an Outybound Entry in We20.The Sender port and receiver port also should be be the ones created in We21 for XI, and SAP+"SYSID" for R3
) Check your PARTENER PROFILE settings ; is IDOC in outbound messages.
2) You may need to check Bussiness System given for Technical System for r3 and in ID check Adapter Specific Identifiers in OBJECTS ->Bussiness System->Service
Go to bd87 and trigger them. You can only trigger the idocs if they are in yellow color. If it is in red it is having an error.
So try to send the one which are in yellow error so that we can see whether it is reaching XI or not. If everything is OK then you should see the idoc in sxmb_moni.
Please see the below links ,
/people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
idocs - /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
note:reward points if solution found helpfull.....
regards
chandrakanth.k

SAP GRC NF-e 10.0 - Problema durante Upgrade (mensagem /XNFE/APP 011)

Boa tarde a todos!
Realizamos o "Upgrade" do SAP GRC NF-e da versão 1.0 para a versão 10.0 (SLL-NFE 900, nível 0008) e estamos convivendo com um problema em uma mensagem XML do PI.
Na transação SXMB_MONI, monitor de mensagens processadas, ao filtrar por mensagens com SELSTAT = 017 Application Error - Manual Restart Possible, encontramos problemas em mensagens do seguinte tipo:
Sender: BATCH_BatchProcess_006
Receiver: CLNT100TND (Mandante 100 do Sistema TND)
Receiver Interface Namespace: http://sap.com/xi/NFE/006
Receiver Interface: BATCH_nfeRecepcaoLoteResponse_IB
Para estes, quando vou até o detalhe da mensagem e seleciono "Call Inbound Proxy" (com status vermelho), em "Payloads", vejo o erro "Não existe ID de lote 000000000000000".
Pelo que vi na tabela T100, a mensagem se refere ao código /XNFE/APP, número 011.
Por que será que está acontecendo este erro? Alguém já vivenciou esta situação antes?
P.S.: Já abri chamado na SAP e eles encaminharam o problema para a SAP Alemanha...
Obrigado,
Daniel

Bom dia Fernando (que bom te encontrar aqui também :-)!
Então, o Denny da SAP Alemanha me retornou dizendo que temos que instalar o XI Content SLL-NFE 10.0 e criar novamente os cenários da NF-e.
Eu estou entrando em contato com o nosso Basis que fica em Lima para ver se é possível que ele instale este componente, para que eu crie novamente os cenários da NF-e (extensão _900).
Após a recriação dos cenários, será que eu consigo reenviar as NF-e de teste novamente ou terei que estornar os documentos e fazer os processos novamente?
Obrigado pela ajuda!
Att.
Daniel

Problem in SXMB_MONI

Similar Messages

Maybe you are looking for