on 10-14-2020 8:51 PM
Hi Mates
How are you all doing?
Does anyone have a list of all V2 (Delivery output) routines and what they do?
From what I know there is no detailed documentation provided by SAP on every standard output routine. Sometimes you might encounter some information on output routines by searching in the support portal by include name, e.g. LV61B003, but this is rare, there are not many corrections for output routines.
Frankly, I never thought of this as a real problem - there are not so many standard routines per application (for V2 output I see only 26 in our sandbox - I used table TFRM with selection per GRPZE, KAPPL and GRPNO) , the code for output requirements is usually very simple and it is quite easy to troubleshoot output requirements via debugging.
Regarding the actual problem that you have (that at the time of goods issue you do not have all information that you need to issue the printout correctly): it is not easy to help without more specific information, but have you considered using activity profiles from transportation? In general - how do you know that you have all needed information to issue the output (based on what criterion)? If you know at which stage you have all needed information then it should be easy to check if an existing standard routine could help you.
Considering that output re-determination happens when a delivery is changed - after goods issue you do not have so many opportunities to do so. Usually in such cases the output is determined at an earlier stage, but is processed later.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi veselina.peykova
Thanks for your info.
What I am trying to build is an alert. Customer service email alert. (BTW we don't have a transportation module). Every time our 3PL (Third-party logistics) partially fulfills a delivery and sends an EDI 945 back, then CS team needs to know that it was short shipped.
So, the idea is to have the 945 IDOC processed. That means the delivery qties get updated according to short shipped qties. Then, what I did, after PGI the output is generated. However, I manually went to delivery, made the changes, then pressed PGI from delivery. Then output was generated but no correct since changes that happened in delivery were never accounted for. That means the change of qties were still not committed to DB. That is what I was trying to find a routine that has more time, so it gives a chance for the commintment of info in DBs.
Hey Carlos
Did you check in NACE transaction
Condition records, Procedures and Access sequences?
Not sure what you mean by Routine should be in one of the above?
Regards
Vinita
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vinita
Thanks for checking my question. And sorry, let me try to explain it a bit better. I created an output, and I added a requirement for this to be generated. This requirement is routine 1. That requirement is to only allow the output to be generated after the PGI is performed. However when output is generated some of the tables I need info from don't have the table commitment done yet. Therefore my output is not correct.
So, what I am trying to do is to see if any pre-existing routines can help me slow down (even more) the process of the output creation. That is why I am looking for a document that has all standard routines (e.g. 1 Delivery GI posted, 3 Delivery Note, 10 Credit Check Block, 12 QualtyCertifDelvItm1, etc...) so I can see if I can use and not have to create any Z one.
Can you please let me know?
User | Count |
---|---|
99 | |
11 | |
10 | |
6 | |
5 | |
5 | |
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.