on 02-11-2014 7:49 AM
Hello,
We have been detected since a long time ago, that output message with
out
condition record is generated, so, this cause a problem because some
output will be sent by EDI to the customer or WMS.
We have several cases per day with this topic
Iin the trace log on NACH table, never sales document output
type Z* had a condition record, and message have been automatically
sent.
This is a case from billing documents, but this issue have been
reportedtoo for delivery outputs to WMS.
Do you remember any simlar case in other customers?
Regards,
felix,
It looks like this problem is occurring for orders, deliveries. Please confirm.
Is it for one or many output condition type?
For this output condition type, what is the access sequence?
In the access seq, how many tables? and what are the fields of each table?
In table NACH, if you give the output condition type, there are zero entries for combination with sales doc type?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello TW,
Yes we have similar issues in output from deliveries and billing.
For the case we have 5 sequence access, with 4 fields, one table per sequence access.
In NACH there is no record possible to determine the output.
In the other cases, for example, deliveries, we have an special problem too: we have an output created with dispatch time=1. But later sometimes the output is generated with dispact time.
In all case there is no determination output analyze to search a possible root cause.
felix,
Let us take delivery output.
When delivery is created, an output is generated. Check the output type, in the delivery.
In table NACH, give that delivery type (KSCHL) and execute. Do you see any condition records?
Also, in VV33, give the condition type, and other information, to check if condition records exist.
Without condition records, output can not be generated!
(as you know) Output works on condition technique.
To me it looks, originally one EDI is triggered and then whenever there is a change is made, the same output might have re-triggered. Not sure how to substantiate, but can you check in the SPRO for the output type, Multiple issue box is checked or not. Also check whether the field do not write processing log box is checked or not. If checked, then remove the check and test again.
Regards,
Hello.
I have checked customizing and for this 2 output, for deliveries and billing is not flagged on 'multiple issing' and 'do not processing log'.
See both attached files, as you can see there is no out put in nast for ZRE4 and SP 2*1762 sales document and on trace log by SCU3, Nach, and the output is created.
As you can see on nast, field NAUTO=X, so in a momment have been determined automatically.
Could be the data possible for determine is being missed in any user exit or standard, but it is dificult to see if we don't have the determination analysis.
Do you know the data base table where is stored the determination analysys?
This is very extrange, we have cases like this in deliveries, invoices, could be there is a bug in standard?
Thank you both,
felix,
The output condition type is ZEN1
From your post, billing type = ZRE4 and SP customer = 2*1762. Confirm
In NACH, what is the extra F1 (apart from ZRE4 and 2*17*)?
NAST is only giving the information when output was created. Run a test now, and let us see if output is created. Paste the screenshot of this table.
Hello,
ZRE4 is sales document type, F1 is customer commonication.
This is the access and consequently vakey...
Sales org./Payer/Communic./SalesDocTy
The sales document type, is retrived on user exit enhancement:
FORM userexit_komkbv3_fill of RVCOMFZZ
IF COM_VBRP_TAB[] is not initial.
LOOP AT COM_VBRP_TAB WHERE AUBEL IS NOT INITIAL.
* Get any position
SELECT SINGLE AUART
FROM VBAK
INTO COM_KBV3-ZZAUART
WHERE VBELN EQ COM_VBRP_TAB-AUBEL.
* if found exit
IF SY-SUBRC EQ 0.
EXIT.
ENDIF.
ENDLOOP.
ENDIF.
I repeat my maial below again, there is no record B505 and consequently in NACH...
If you try to reproduce in test system the message is not generated, but on live system is happening all days.
User | Count |
---|---|
102 | |
12 | |
11 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.