on 2008 Jan 21 3:01 PM
I need some type of help/documentation on Tcode OPK8. I want/need to automatically create an iDoc or an output (iDoc is preferred) at the save (creation and change) of a production order (for specific plants). I assume that I can control this in OPK8 but I can't find any information.
Regards,
Davis
You can give a print out during saving
In OPK8...Flow control transaction option
for a given plant and transaction you selcet radio button - online...then itb will work. For Idoc you need to define a new output type and give out put with Idoc...you need to set with ABAPer/basis guy to design the new output type with idoc option.
For more details read below
print procedure
Flow control for transactions
You can use flow control to determine for each plant and transaction whether printing is to take place online on updating or in the background. The print mode that you choose here is just a default and can be changed in the actual transaction.
Example
Plant TCode Online Backgr. Update
**masked** XXXX **masked** x
Here it is specified that the mode of processing "background printing" is to be proposed in each plant and for all transactions.
come back if required
Edited by: Rajesha Vittal on Jan 21, 2008 7:15 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Rajesha. What I am looking for, in the end, is a way to send an idoc to an external Shopfloor system on the change and creation of certain production orders (based on plant). The way a past programmer solved this issue was to guess the next prod order number in order to create the idoc on the save of the prod order. This worked most of the time but now we are changing the way we create production orders so we are getting duplicate numbers.
Anyway, what I was hoping for was a way to automatically send off an idoc or a way to mark a production order for later (to create the idoc at a later time). The best we could come up with is to append a flag to the production order which would indicate that an idoc has, or has not, been sent. I believe that is what we will use unless there is a standard way to do this in SAP. I would imagine that SAP has taken care of it already but we can't seem to find it.
Regards,
Davis
Yes I did, well, I tried all user exits on tcodes CO01 and CO02. I even tried the user exits at the save of the sales order. I was hoping that the sales order saved after the production order was saved (in our flow) but that isn't the case. I believe we will have to resort to appending a field onto AFKO that acts as a flag. We will then use a bit of overlap (based on past production order numbers) and run a batch job that creates idocs and sends them off. I can't believe that SAP doesn't have anything but the closest I can find is a tcode that you run after the production order is saved but this is only tailored to their shop floor system and you must know the production order number. I know what we need isn't unique, there is no way that it can be.
Regards,
Davis
User | Count |
---|---|
101 | |
8 | |
6 | |
5 | |
5 | |
4 | |
4 | |
4 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.