on 07-20-2007 11:29 AM
Hi
We have set up an interface that posts invoice data to R/3 . At runtime , in SXMB_moni all the messages have a chequered flag but the invoice is not getting created in R/3 for some reason unknown. Being this the case, we are getting back response from R/3, which we are posting to a database. The response, however does not contain the Invoice no.
What do you think is the cause of the problem?
We also wanted to check the outbound RFC data flowing to the R/3 system in RWB under message monitoring but we get a message like "Message deleted to save space" .
Any help will be highly appreciated
hi,
d>>>At runtime , in SXMB_moni all the messages have a chequered flag but the invoice is not getting created in R/3 for some reason unknown.
what has XI message status to do with posting an invoice?
if you used idocs and aleaud you'd see the error in R3 (and XI)
if you use RFc then you see the error in bapi ret
>>>The response, however does not contain the Invoice no.
it's never there if you have an error
if you designed your process correctly
you should be able to track the error and reprocess
it from R3 (idoc or abap proxy) it not I suggest
thinking about the process more carefully as you may have
many problems when posting invoices...
and if you don't see (and cannot reprocess) a simple error
that's a dissaster..
Regards,
michal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
any reason why the invoice is not getting posted??
regards
krishna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you have the Commit record flagged in Integration Directory?
(that is asuming you using RFC..)
Try extending the trace file..
Traces are used to analyze runtime errors. By setting a specific trace level for specific locations, you can analyze the behavior of individual code segments at class and method level. This is done with the help of the log configurator service:
 Services
 Log Configurator
 Locations
 Choose the location (Java package) and the tracing level (severity)
(for example, com.sap.aii.adapter.rfc)
 Root Location > com > sap > aii > rfc
 Set the severity and choose Copy Severity to Subtree.
Also check OSS Note 730870
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
I have included the check flag in ID . No i am getting a BAPI return message in sxmb_moni like
com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: failed to parse BAPI response due to: com.sap.aii.af.rfc.util.bapi.BapiException: Parameter with name RETURN not found.
how do i correct it?
regards
krishna
Yes, We are creating the invoice in R/3.
and we are not able to get the invoice no as response
Thanks , we shall try the scenario with the return parameter set.
also, we are wondering why the invoice isnt created at R/3 side? when we execute the Tcode , it is not returning any Invoices.
rregards
krishna
okie it is not a bapi infact but a t-rfc f/n module. maybe some of the screen sequence is inconsistent with certain datas. the best thing to do is create a invoice manuaaly and see for any errors with the existing data. or change the mode in the BDC to "A" and execture the f/n module with ur data fedin manualy in se37. there u can troubleshoot
for all the bapi i'd worked on so far the status is posted into the return strucutre either sucessful or failure. since the system reutrn code is always 0 for a bapi even if a transaction tosses for an error we need to have the status tracked in return parameter
"BAPIs themselves must not trigger any messages (such as MESSAGE xnnn) in the coding. In particular they must not generate terminations or display dialog boxes. Instead, all messages must be intercepted internally and reported back to the calling program in the Return parameter. Otherwise the BAPI will not be processed correctly and control may not be given back to the calling program "
http://help.sap.com/saphelp_nw04/helpdata/en/a5/3ec9f74ac011d1894e0000e829fbbd/frameset.htm
Message was edited by:
Prabhu S
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.