Transaction IW22 and FCode WOAB

I am using the user exit EXIT_SAPMIWO0_020 quiet sucessfully to reverse a material document using MBST and writing the details of the notification to a custom table when a user has cancelled a PM notification (Definition of a cancelled notification is when the TPLNR, EQUNR and BAUTL field are all = to SPACE) and saved it.
I have then written a BDC program to call IW22 and de-allocate any associated orders and set the status NOCO and DLFL to prepare them for archive based on a search of a custom table. This program will be set up to run overnight to capture any notifications cancelled that day and process them accordingly.
The difficulty I am having is with the BDC calling Fcode WOAB, if I run through the BDC in Mode A and debug it, it works fine. The program displays each screen in turn as expected and completes without any errors.
If I run through it in mode E and debug, the program stops at the point where WOAB is called and I get the error message 00 344 "No batch input data for screen & & "
If I run the program with Mode N and outside debug the BDC the program does not carry out the de-allocation of the order.
I checked my MESSTAB in my program in Mode E and got message 00 344 "No batch input data for screen & & ", but I cannot see where or what the screen needs to process it.
I have also searched OSS with the FCode WOAB and came across 1 likely note but it applies to version 4.xx we are only on 3.1i, the function module referenced in the note does not exist in our system.
I have also searched OSS with the program name SAPMIWO0 and screen 2100.
The program to call IW22 and looks at a custom table for entries for a specific date that the user enters or from a variant, the default is sy-datum.
Thanks,
Dave

Anyone got any help on this one please?
all help appreciated.
Dave
Message was edited by: David Lawlor

Similar Messages

What is the BADI for the transaction IW21 and IW22

Hi,
I am working on one issue on IW21. I created one PM creation using Tcode IW21 and same PM I see on IW22 and in tab "Sheduling Overview " one field 'Start Date' is showing today's date.
My requirement is to keep blank that field 'Start Date' .
So Can anyone give any proper BADI to achieve this functionality.
Waiting for quick response.
Best Regards,
BDP

hi..
These are the following Bxits and Badi available for Tcode IW21 and 22.
_Exit Name           Description_
IWO10026            User check on setting status 'Do not perform'
IWO10027            User exit: Generate user-defined settlement rule
IWOC0001            Create PM/SM notification: Determine reference object
IWOC0002            PM/SM notification: Check whether status change is allowed
IWOC0003            PM/SM authorization check of ref. object and planner group
IWOC0004            Change single-level list editing PM/QM/SM ALV settings
_Badi Name            Description_
IQS_MASS_CHANGE      Mass Change of Notifications
IWO1_SUBSCREEN_0170 Display Additional Data on Object Screen 0170 in Maint. Plan
Thanks,
Padma

Add new fields in SAP transaction IW22

Hello,
I want to add 2 new fields in SAP standard transaction IW22. I checked the package for this transaction and it is IWOC. I searched the exits for package IWOC but was not able to find any screen exits for it.
Kindly help me on how I should proceed with it.
Regards,
Parag

Please check these
User exit/ Business Add-in              Description
User exit
IWO10026                                User check on setting status 'Do not perform'
IWO10027                                User exit: Generate user-defined settlement rule
IWOC0001                                Create PM/SM notification: Determine reference object
IWOC0002                                PM/SM notification: Check whether status change is allowed
IWOC0003                                PM/SM authorization check of ref. object and planner group
IWOC0004                                Change single-level list editing PM/QM/SM ALV settings
Business Add-in
IQS_MASS_CHANGE                         BadI for Mass Changes to Notifications
IQS0_STATUS_MAINTAIN                    Control of Changeability of User Status
NOTIF_AUTHORITY_01                      Additional Authorization Checks for the Notification
WOC_FL_DETERMINE                        Determine Date for Determining Installation Loc. Equi.
IWOC_OBJECTINFO_CHNG                    Changes to Data of Object Info Screen
IWOC_LIST_TUNING                        Performance Tuning for Lists in PM/CS
IWO1_SUBSCREEN_0170                     Display Additional Data on Object Screen 0170 PhysicalSample

Modifications in field LONG TEXT in transaction IW22

Hello friends!
I have the following problem:
I need to allow modifications in field LONG TEXT in transaction IW22 until the notification is realeased, the thing is that this field gets inactive and it doesn't accept further modifications, can anybody help me??
Thanks in advance,
Frinee

Peculiar - I was just looking at this (for a different problem). Look at OSS note #876698.
Rob

There are two transactions ZJPVCS303 and ZJPVCS303_US for one single Report

When run as a batch program, (currently this is the case), or withT-Code ZJPVCS303 the selection screen is unchanged (except for additional sales area above)
- When run as T-Code ZJPVCS303_UL (UL stands for Upload) the selection screen is changed. The unix file option is no longer available, and the user is able to upload a local file (in the same format as the current unix file, but tab delimited) to the program for processing.
Requirements:
There are two transactions ZJPVCS303 and ZJPVCS303_US for one single Report.
->When ZJPVCS303 Transaction is executed, the file is uploaded from the Application
server to SAP R/3. The selection screen parameters would be:
Logical Filename:
Sales Organization:
Distribution Channel:
Division:
->When ZJPVCS303_US Transaction is executed, the file is uploaded from the Presentation Server
to SAP R/3. When this transaction is executed, it should not have the 'Logical
Filename' parameter anymore on the selection-screen. Instead it should only have
Local File name on the presentation server:
Sales Organization:
Distribution Channel:
Division:
    The same thing is applicable for the other transaction ZJPVCS303. When transaction ZJPVCS303
is executed, it should not have the 'Local Filename' parameter anymore on the selection-screen. Instead it should only have
Logical Filename:
Sales Organization:
Distribution Channel:
Division:
So how should I make these parameters invisible depending on the transaction codes execution.
I have an idea of using MODIF ID, LOOPING AT SCREEN...MODIFY SCREEN.
I have an idea of using SY-TCODE.
EX:
AT SELECTION-SCREEN OUTPUT.
IF SY-TCODE = 'ZJPVCS303'.
LOOP AT SCREEN.
IF SCREEN-GROUPID = 'GRP'.
   SCREEN-INPUT   = 0.
   SCREEN-INVISIBLE = 1.
   MODIFY SCREEN.
ENDIF.
ENDLOOP.
ELSEIF SY-TCODE = 'ZJPVCS303_US'.
LOOP AT SCREEN.
IF .....
ENDLOOP.
ENDIF.
ENDIF.
But I am not able to get the output which I require. Please help me out.

Hello Rani
Basically the transaction determines whether upload starts from application server (AS) or presentation server (PC). Thus, you will have the following parameter:
PARAMETERS:
p_as_fil          TYPE filename   MODIF ID unx, " e.g. Unix server
p_pc_fil          TYPE filename   MODIF ID wnd. " e.g. Windows PC
AT SELECTION-SCREEN OUTPUT.
CASE syst-tcode.
*   transaction(s) for upload from server (AS)
    WHEN 'ZJPVCS303.
      LOOP AT screen.
        IF ( screen-group1 = 'UNX' ).
          screen-input = 0.
          screen-invisible = 1.
          MODIFY screen.
        ENDIF.
      ENDLOOP.
*   transaction(s) for upload from local PC (PC)
    WHEN 'ZJPVCS303_US.
      LOOP AT screen.
        IF ( screen-group1 = 'WND' ).
          screen-input = 0.
          screen-invisible = 1.
          MODIFY screen.
        ENDIF.
      ENDLOOP.
   WHEN others.
   ENDCASE.
Regards
Uwe

What is the diff b/w transactional cube and std cube

What is the diff b/w transactional cube and std cube

Hi Main differences,
1) Trasactional infocube are optimized for writing data that is multiple user can simultaneously write data into it without much effect on the performance where as the std infocube are optimized to read the data ie.e through queries.
2) transactional inofcubes can be loaded through SEM process as well normal laoding process.Std can be loaded only thorugh normal loading process.
3) the way data is stored is same but the indexing and partionong aspects are different since one is optimized for writing and another one for reading.
Thanks
Message was edited by:
Ajeet Singh

Monitoring of remote system's Transactional RFC and Queued RFC

Hello,
In our production system, in rz20- CCMS monitor templates- Communication-Transactional RFC and Queued RFc- outbound queues- Queues otherwise not monitored we can see blocked queues for each client.
System is connected to solution manager and we wish the central auto reaction is implemented in solution manager
However i am unable to find Transactional RFC and Queued RFC for the remote system, they exist only for solution manager itself
Tell me how can i do the central monitoring

Hello,
First you need to check with your Landscape in solman in order to monitor any kind of activities to do so pls follow these steps.
Go to SMSY in solman under Landscape components>Product systemsselect you satellite system example SAP ECC.
On the main screen you will find client for which you have generated RFC connection. Please check though connection are working fine, Go to edit mode and try to click on generate button there will be a pop-up, which gives a clear picture of RFC connection which already exists, and you can also re-generate this RFC connection by clean it up when you re-generate pls select under Actions after generation assign RFC dest for system monitoring.
But make sure there is no project impact on this RFC, like they are not using any logical components and already have some projects running on this RFC connection.
I would advise you to first you the option of assign and check RFC button which is next to generate icon.
Regards
JUDE

CALL TRANSACTION 'MIR6' AND SKIP FIRST SCREEN .

Hi all,
i hope there is someone that can help me.
My problem is: in an ABAP custom report in a FORM user-command my code is
CASE ls_selfield-sel_tab_field.
    WHEN 'ITAB-BELNR'.
      IF NOT ls_selfield-value IS INITIAL.
        SET PARAMETER ID 'RBN' FIELD ls_selfield-value.
        CALL TRANSACTION 'MIR6' AND SKIP FIRST SCREEN .
ENDCASE.
When i click on output field of my report, not skip first screen but only call MIR6!!!
How can i solve this problem?
Regards.

Hi,
First of all Please don't use all Caps for Subject Line
Test Following Sample Code it will solve out your problem,
DATA: it_bdcdata TYPE TABLE OF bdcdata,
      wa_it_bdcdata LIKE LINE OF it_bdcdata,
      belnr(10).
belnr = '100'. " Give Document Number here
DATA opt TYPE ctu_params.
CLEAR wa_it_bdcdata.
wa_it_bdcdata-program = 'SAPMM08N'.
wa_it_bdcdata-dynpro   = '100'.
wa_it_bdcdata-dynbegin = 'X'.
APPEND wa_it_bdcdata TO it_bdcdata.
CLEAR wa_it_bdcdata.
wa_it_bdcdata-fnam = 'BDC_CURSOR'.
wa_it_bdcdata-fval = 'SO_BELNR-LOW'.
APPEND wa_it_bdcdata TO it_bdcdata.
CLEAR wa_it_bdcdata.
wa_it_bdcdata-fnam = 'SO_BELNR-LOW'.
wa_it_bdcdata-fval = BELNR.
APPEND wa_it_bdcdata TO it_bdcdata.
CLEAR wa_it_bdcdata.
wa_it_bdcdata-fnam = 'BDC_OKCODE'.
wa_it_bdcdata-fval = '=CRET'.
APPEND wa_it_bdcdata TO it_bdcdata.
opt-dismode = 'E'.
CALL TRANSACTION 'MIR6' USING it_bdcdata OPTIONS FROM opt.
Please Reply if any Issue,
Best Regards,
Faisal

Call transaction 'LS33' and skip first screen.

This doesn't work:
set parameter id 'LEN' field '04018091'.
call transaction 'LS33' and skip first screen.
I've found this:
<a href="https://www.sdn.sap.com/irj/sdn/message?messageID=3715690">https://www.sdn.sap.com/irj/sdn/message?messageID=3715690</a>
but I'm not sure about the exact meaning (wouldn't know where to put the *)
nor even about if it applies.
Thanks in advance.

Sorry, I mistook this forum for that of ABAP General.
Anyway, the answer is in
Call transaction 'LS33' and skip first screen.

CALL TRANSACTION 'ME23N' AND SKIP FIRST SCREEN.

Hi,
i'm using this in an report.
SET PARAMETER ID 'BES' FIELD WA_ITAB-EBELN.
SET PARAMETER ID 'BSP' FIELD WA_ITAB-EBELP.
CALL TRANSACTION 'ME23N' AND SKIP FIRST SCREEN.
It works OK.
Is there any parameter ID to go in a sprecial part of an PO, for example
direct to materialdata or konditions?.
thanks.
Regards, Dieter

Hi,
I think u can do that by using BDC as used in this code please refer to this code.
FORM get_user_command USING cr_ucomm     LIKE sy-ucomm      "#EC *
                            cr_selfield TYPE slis_selfield.
CLEAR wa_final.
DATA BEGIN OF bdcdata OCCURS 10.
          INCLUDE STRUCTURE bdcdata.
DATA END OF bdcdata.
CASE cr_ucomm.
    WHEN '&IC1'.
      READ TABLE it_final INTO wa_final
               INDEX cr_selfield-tabindex.
      IF cr_selfield-fieldname = 'MATNR'.
        IF sy-subrc IS INITIAL.
          SET PARAMETER ID 'MXX' FIELD 'E'.
          SET PARAMETER ID 'MAT' FIELD wa_final-matnr.
          SET PARAMETER ID 'WRK' FIELD wa_final-werks.
          CALL TRANSACTION 'MM03' AND SKIP FIRST SCREEN.
        ENDIF.
      ELSEIF cr_selfield-fieldname = 'LIFNR'.
        IF sy-subrc IS INITIAL.
          CLEAR bdcdata.
          bdcdata-program = 'SAPMF02K'.
          bdcdata-dynpro   = '0101'.
          bdcdata-dynbegin = 'X'.
          APPEND bdcdata.
          CLEAR bdcdata.
          bdcdata-fnam     = 'RF02K-LIFNR'.
          bdcdata-fval     = wa_final-lifnr.
          APPEND bdcdata.
          CLEAR bdcdata.
          bdcdata-fnam     = 'RF02K-EKORG '.
          bdcdata-fval     = wa_final-ekorg.
          APPEND bdcdata.
          CLEAR bdcdata.
          bdcdata-fnam     = 'RF02K-D0310'.
          bdcdata-fval     = 'X'.
          APPEND bdcdata.
          CLEAR bdcdata.
          bdcdata-fnam     = 'WRF02K-D0320'.
          bdcdata-fval     = 'X'.
          APPEND bdcdata.
          CLEAR bdcdata.
          bdcdata-fnam     = 'BDC_OKCODE'.
          bdcdata-fval     = '/00'.
          APPEND bdcdata.
          CLEAR bdcdata.
          bdcdata-program = 'SAPMF02K'.
          bdcdata-dynpro   = '0110'.
          bdcdata-dynbegin = 'X'.
          APPEND bdcdata.
          CALL TRANSACTION 'XK03' USING bdcdata MODE 'E'.
        ENDIF.
      ENDIF.
ENDCASE.
ENDFORM. " get_user_command
regards,
sudha

CALL TRANSACTION 'VA02' AND SKIP FIRST SCREEN?

Hi, Gurus:
In my program, after I call 'CALL TRANSACTION 'VA02' AND SKIP FIRST SCREEN.'    in the va02, user maybe do some change and save
then I want to get those change as the dollowing:
    select single uvall into c_complete_flag from vbuk
     where vbeln = lv_vbeln.
why I can't get the latest change.
Thanks,

VA02 usese the asynchronus update mehtod so, it gives you the message like "Order 1111 was saved" but the database update is still going on.
So, you need to wait for some time before facthing the data from the database.
You can use like:
WAIT UP TO 10 SECONDS.
But this statement will force you to wait for atleast 10 seconds before doing any thing.
Regards,
Naimesh Patel

Is the concept of Transactional DSO and Cube in BI 7?

Hi,
Is the concept of Transactional DSO and Cube in BI 7?
I see 3 type of Cubes[Standard or VirtualProvider (Based on DTP, BAPI or Function Module)]
but canu2019t see transaction Cube.
also
I see 3 type of DSO(Standard, Write-optimized, Direct update )
but canu2019t see transaction DSO
See this link on DSO, with examples etc:
http://help.sap.com/saphelp_nw04s/helpdata/en/F9/45503C242B4A67E10000000A114084/content.htm
I am looking for such summary also for Cubes have you see a similar one?
Thanks

New terminology in BI 7.x
Transactional ODS = DSO for direct update
Transactional Cube = Realtime Cube
Jen

Block size in tt for writing data to transaction log and checkpoint files

Hello,
what block size is TimesTen using when its writing data to transaction log and checkpoint files? Does it use some fixed block size during filesystem writes?

Although in theory logging can write 2 KB blocks in almost all circumstances it will write 4 KB or larger so yes a filesystem with a 4 KB block size is fine for both checkpointing and logging.
Chris

What is the exact purpose of Transaction NACE and NAST Table?

Hi All,
What is the exact purpose of Transaction NACE and NAST Table?
Pls help me
Akshitha.

Hi
When a Output type in an apllication doc is configured with a Medium, Partner, Lang and other communication paramters an entry is created in NAST table
so to trigger the output an entry in NAST is compulsory
Output is a link between the Driver Program and the Sapscript,
An output type summarizes messages of the same meaning. It contains parameters that are valid for all its assigned messages, for example appropriate partner functions.
Transmission medium is a medium which the layout will be come out, this may be printout, Fax or Mail
Check this link.
http://help.sap.com/saphelp_nw2004s/helpdata/en/c8/19884743b111d1896f0000e8322d00/content.htm
ex-how to config output type.
You will assign output types using Transaction NACE.
Do the follow steps to assign output type
1)Select Application Type V2 which will have description Shipping.
2)Click on Output types button.
3)Go to change mode by pressing Ctrl+F4.
4)Select one output type which already exists
5)Do Copy As(F6)
6)Give your output type against Output Type field.
7)Under General data Tab, Give Program and Form routine and Save the data.
i think it a work of functional guy but at senior level i think it is not a big deal for abaper.
Check the following documentation
In NACE t-codewe have the application for each one. based on the application output type can be defined, based on output type script and print progrma can be defined.
If suppose data can be read from EDI then we should go for condition records.
So whenever we execute the script first composer checks the output type and then execute the program. in program whenever opn form FM will be populate then script will open first. After that again program till another FM will populate if it then script will populate........like it is cycle proces. Composer does all these things and at last it will submit that output to spool.
Go to the Transaction NACE.
choose the related sub module.. like billing or shipping
doubel click on Output Types
Choose the Output Type for which whcih you wanted your script to trigger
Then select the Output Type and double click on Processing Routine
Then go to create new entries--> Select the Medium (1- print output), then enter your Script and Print Program detls --> Save and come out
Now go to the Transaction (for which you have created the output type)... Issue output--> Select the output type --> Print....
Device Types for SAP Output Devices (Detail Information)
Definition
The device type indicates the type of printer to be addressed. When you define an output device, choose the name of the device type that was defined in the SAP System for your printer model, such as Post2 for a PostScript printer. In the case of frontend printing under Microsoft Windows, you can also use the generic (device-independent) device type SWIN.
The system uses the information in the device type to convert a document from the internal SAP character representation (spool request in OTF or in text format) to a device-specific, print-ready data stream (output request). Since a device type specifies attributes that apply to all devices of a certain model, it can be shared among device definitions. For example, all devices in the SAP spool system that are compatible with Hewlett-Packard LaserJet IIID printers would use the HPLJIIID device type.
You should not confuse the device type with the printer driver. The device type is the total of all attributes of an output device that the SAP System must know to control the output device correctly, such as control commands for font selection, page size, character set selection, and so on. These attributes also include the printer driver that SAPscript/Smart Forms (the SAP form processor) should use for this printer. The SAPscript printer driver that is to be used for devices of this type for output formatting is therefore only an attribute that the device type specifies.
How do I choose the correct device type?
In most cases, the SAP System already provides the appropriate device type for the printer type for the printer model that you want to use.
These standard device types are completely defined and need no modification or extension before you use them in device definitions.
You can also download missing device types from the sapserv server. For a current list of the supported device types, see SAP Note 8928 in the SAP Service Marketplace.
Most printers can be controlled using a generic format, such as PostScript. They can be switched to a mode that is compatible with one of the standard printers for which an SAP device type is available. In this case, a supported model is emulated.
Almost all printers are delivered with Microsoft Windows printer drivers. The system can control these printers with the generic (device-independent) device type SWIN. The Microsoft Windows spool system then performs the processing of the print data.
If the specified device types are not available, and generic device types cannot be used, you must create your own device type or edit a copy of an existing device type. We recommend that only those with specialist knowledge of the SAP Spool System and printer driver code do this. For more information, see Defining a New Device Type .
Attributes of a Device Type
A device type is distinguished by the attributes listed below. If you change an existing device type or create a new device type, you must change at least some of these attributes.
Character set: A character set specifies the codes with which characters must be represented in the print-ready output stream (output request). This code replaces the generic SAP characters set that is used internally by the SAP spool system (spool request).
Printer driver: You can specify different printer drivers for printing SAPscript documents and ABAP lists.
Print controls: Print controls represent printer operations, such as boldface or changing the font size. These print control are replaced by printer-specific commands during the creation of the output request from a spool request.
Formats: Formats specify the format supported by the SAP system. The system differentiates between SAPScript formats (DINA4 and LETTER) and ABAP list formats (X_65_132 = 65 rows/132 columns).
Page format: A page format is the interface between a format and SAPscript. It specifies the paper dimensions with which SAPScript can calculate the row and column lengths.
Actions: Actions are output device-specific commands that are required for the implementation of a format. The action printer initialization, for example, can contain a printer command with which the number of rows on a page is defined. There is a set of actions for every format supported by a device type.
Reward points for useful Answers

Transactional Caches and Write Through

I've been trying to implement the use of multiple caches, each with write through, all within a transaction.
     The CacheFactory.commitTransactionCollection(..) method only seems to work correctly if the first transactionMap throws an exception in the database code.
     If the second transactionMap throws exceptions, the caches do not appear to rollback correctly.
     I can wrap the whole operation in a JDBC transaction that rolls back the database correctly but the caches are not all rolled back because they are committed one by one?
     For example, I write to two transaction maps, each one created from separate caches. When commiting the transaction maps, the second transaction map causes a database exception. It appears the first transaction map has already committed its objects and doesn't roll back.
     Is it possible to use Coherence with multiple transaction maps and get all the caches and databases rolled back?
     I've also been trying to look at using coherence-tx.rar as described in the forums within WebLogic but I'm getting @@@@@ Failed to commit: javax.transaction.SystemException: Could not contact coordinator at null+SMARTPC:7001+null+t3+
     (SMARTPC being my pc name)
     Has anybody else had this problem? Bonus points for describing how to fix it!
     Mike

The transaction support in Coherence is for Local     > Transactions. Basically, what this means is that the
     > first phase of the commit ("prepare") acquires locks
     > and ensures that there are no conflicts. The second
     > phase ("commit") does nothing but push data out to
     > the caches.
     This means that once prepare succeeds (all locks acquired), commit will try to copy local data into the base map. If there is a failure on any put, rollback will undo any changes made. All locks are cleared at the end.
     > The problem is that when you are using a
     > CacheStore module, the exception is occurring during
     > the second phase.
     If you start using a CacheStore module, then database update has to be part of the atomic procedure.
     >
     > For this reason, write-through and cache transactions
     > are not a supported combination.
     This is not true for a cache transaction that updaets a single cache entry, right?
     >
     > For single-cache-entry updates, CacheStore operations
     > are fully fault-tolerant in that the cache and
     > database are guaranteed to be consistent during any
     > server failure (including failures during partial
     > updates). While the mechanisms for fault-tolerance
     > vary, this is true for both write-through and
     > write-behind caches.
     For the write-thru case, I believe Database and cache are atomically updated.
     > Coherence does not support two-phase CacheStore
     > operations across multiple CacheStore instances. In
     > other words, if two cache entries are updated,
     > triggering calls to CacheStore modules sitting on
     > separate servers, it is possible for one database
     > update to succeed and for the other to fail.
     But once we have multiple CacheStore modules, then once one atomic write-thru put succeeds that means database is already updated for that specific put. There is no way to roll back the database update (although we can roll back the cache update). Therefore, you may end up in partial commits in such situations where multiple cache entries are updated across different CacheStore modules.
     If I use write-behind CacheStore modules, I can roll back entirely and avoid partial commits? Since writes are not immediately propagated to the database? So in essence, write-behind cache stores are no different than local transactions... Is my understanding correct?

Transaction IW22 and FCode WOAB

Similar Messages

Maybe you are looking for