on 10-07-2014 2:37 PM
We are experiencing very sporadic instances of ASN output conditions not generating, Our company makes hundreds of shipments per month for EDI customers requiring ASNs, but we have had 14 instances since February of this year where the ASN output condition was not created at the time of shipment completion when the ASN is normally generated. The instances are spread across nine different customers and four different plants that ship to these customers. We have been on ECC 6.0 (since February, 2013) and are currently on Enhancement Pack 5. We are not able to determine any common issue across these shipments that might lead to the ASN output not being generated. Scanning SAP Notes has not led us to find any identified fix, nor have we been able to duplicate the issue in our QAS system. Any advice on what to look for to resolve this issue that has affected our supplier rating in a couple of cases?
Hi Jeff,
In shipment there is a report called RB56ABST (if I remember name correctly) which trigger outputs from delivery based on shipment event. Now in your case this report is set to trigger ASN from delivery at shipment completion..... Please check your customization setting to findout variant name created in this report which is assigned to Shipment completion button...
For example after leg determination user removed check and changes delivery itinarary or removed delivery may lead some delivery not assigned to shipment stages.
This may be reason causing such issue.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For those shipment without ASN output, in VT02N --> From menu Goto --> Output
From menu --> Goto -> Determination Analysis.
For the required output type and access sequence, check what is the log message there. Screen shot to use if possible.
In SPRO -> LE -> Transportation -> Basic Transportation functions -> output control -> Maintain output determination procedures. Check what is the determination requirement for your assigned procedures. Do a debug in your requirement routine if required to check in detail what fails.
Jeff, as correctly pointed out, please clarify what exactly triggers ASN in your case. Also the output determination analysis screen would be the obvious and first place to check for any issues with triggering output. Check for the update terminations in SM13 as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for the reply and suggestions.
The ASN is triggered upon goods issue which is triggered by the Shipment Completion button with VT02N.
There is no output determination analysis log for any of the shipments where this has occurred (14 times identified since February). The ASN output simply does not generate. I have not seen any update terminations in SM13 either.
Check condition record.
Check output determination requirement routine.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How currently the ASN is being generated? With the standard configuration in SAP?
Though you have indicated that this issue is arising once in a while and it is very difficult to find out the exact root case, you can check the above areas I listed with those shipments where ASN was not generated
G. Lakshmipathi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for your reply and suggestions.
The ASN is being generated as an output from the shipment in VT02N, upon goods issue as triggered by the Shipment Completion button. An IDOC is created for 856 ASN transmission through XI to our customers.
Not sure what you mean by "DA" in relation to goods issue. Goods issue posted successfully in all cases with the Bill of Lading output form successfully generated, just no ASN.
No change in route or shipping condition before or after goods issue.
User | Count |
---|---|
85 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.