Row error in Sales Orden b1

Hi experts, here againt make questions
This is the SAP Message
DOCUMENTS ROWS CAN NOT BE CLOSED CONCURRENTLY  WITH THE OTHER DOCUMENT MODIFICATIONS YOU HAVE MADE  [SALES ORDER ROW- STATUS] LINE MESSAGE 131.-177]
The action is in Sales order and need close  rows in the document, sales order type Item.
Thanks for your kind attention.
Regards.

Thanks Gordon but what´s mean FMS con you explain more.
Thanks.

Similar Messages

  • How to close a row in a Sales Order?

    Hi ,
    How can i close a row in a sales order , I can do it in the purchase order, but in the sales order if i have two or more items of which i need to close one, i cannot do so as it gives an error.
    SAP version used 2005B PL41.
    Jyoti

    Hi Jyoti
    Do you have any Formatted Searches that are set as "Refresh Regularly". If so, you must hit Update for the S/O first before attempting to close any rows. If you open a Sales Order and the OK button changes immediately to Update, then this is the case.
    Kind regards
    Peter Juby

  • Query to check item no in all the rows in a sales order

    Dear All,
    Please assist me with a query which would be able to check the rows in a sales order to see if a particular item no is present. We are using SAP B1 2005 PL50
    Kind Regards,
    Monil.

    Hi !
    Try this !
    if @object_type = '17' and @transaction_type IN ('A', 'U')
    BEGIN
    if not exists (select t0.docentry from ORDR T0,RDR1 T1 where
    t0.Docentry = @list_of_cols_val_tab_del and
    t0.Docentry=T1.Docentry and
    T1.Itemcode in (select o1.itemcode from oitm o1) and T1.Itemcode = 'XXXXX'
    begin
    select @error = 1, @error_message = 'Add the item'
    end
    end
    Replace XXXXXX with your itemcode !

  • Sending goods error in sales order

    Hi guru ,
    i am facing one error in sales process in sap sd, that error , i am sending the goods to  the customer , conforms  quantity  5  that system send to customer 10 quantity  , what is happened here , and what will i do sir  , plz tell me sir

    Hello,
    Check the change log in Delivery
    Menu: Environment --> changes
    Check if anybody has changed the delivery qty in delivery manually.
    Also check your picking qty, GI qty in your material document..
    thank you
    Venkatesh

  • Error in Sales order - Consumption account not found

    Hi Gurus,
    I am facing an error in Sales order - 'Consumption account not found'. The scenario is third party. In sales order, it says 'Consumption account not found'. the item category is TAS and scedule line category has general modification key 'VKA'. And as it is third party, thr is no movement type for the schedule line category. The valuation  class of the material is 3334 (software services). I was thinking In OBYC, under GBB key, this combination of my val. grping code+ 3334 + VKA and relevant GLs shud exist.
    But in my development client, i dont get any error for the same material. And in thr also, thr is no mention of entry like above combination in OBYC. So its making me think that its not config error. But its an issue of master data or GL data.
    Please help me . This is critical.
    -Prashant

    Hi,
    Your observation is perfectly write, the possible errors are
    1.  Check the combination of Account modifier of Purchase order account assignmnet or PR.  Based on the modifier and check the relevent combination in OBYC
    Valuation ClassAccount ModifierIf Groups is there + Transaction Event Key + Gl Accounts
    2.  If GL Account is available then check the GL Master through FS00 for validation of mandatory consumption is required and i feel there is no issue with material master.
    Rewards if it helps
    Regards
    Goutham

  • Error in sales order when selecting a warranty item in configurator 'Please enter required information - Service Reference Type Code'

    Error in sales order when selecting a warranty item in configurator 'Please enter required information - Service Reference Type Code'
    Not able to book the sales order because of this issue

    Order Management does not support the inclusion of optional service items in a configured Model BOM (see Support article #1296751.1 for more detail).  Allowing for such would therefore require customization.
    As you've found, there's no modeling restriction that prevents you from creating a Model BOM that includes optional service items, nor is there any problem with creating a Configurator Model for it.  And required service items (such as a warranty item that is a required child of an optional BOM component) do not present a problem; they have nothing to do with Configurator, and would never appear as sub-lines in OM.  The problem arises in OM, which requires that any service item be "associated" to the item it's "servicing".  OM does not automatically make such an association with service sub-lines, even though it might be argued that an association may be inferred by the BOM structure (i.e., OM does not assume that an optional service sub-line is necessarily associated, from a service standpoint, with its BOM parent).  OM customization is therefore required in order to hook any service item up to its corresponding product item.  Many customers who configure service along with product have implemented such a customization.
    (Another gap in such a solution that may be relevant to you is that for an included optional service item requiring recurring billing, Order Management does not create the requisite Service Contract.  Customers have likewise developed customizations to address this, as well.)
    As this is not specifically a Configurator matter (you could have created your order without using Configurator at all, and you would have experienced the exact same behavior), please do not take my explanation as being either authoritative or comprehensive (I am a Configurator expert, and only knowledgeable enough about Order Management to be dangerous).  It would be advisable for you to seek more detailed information/recommendations from the Order Management forum.
    Eogan

  • Closing / Cancell Date of Row Item in Sales Order

    Dear All
    We have to generate one report for one of our customer, which requires to know the 'Cancell / Closing Date' at row level of Sales Order. We could not found it in 'RDR1' table. 'Cancell / Closing Date' only available in header table i.e. in ORDR table. But if any row is closed or cancelled then that is not reflected in header table. So please let us know how to know the 'Cancell / Close Date' in row level in SO.
    Thanks & with regards
    Aloke Bandyopadhyay

    Dear Aloke,
    You may check ADO1 table for historical record to find it.
    Something like:
    SELECT T1.DocNum, T1.DocDate, T0.Linenum+1 'Line#', T0.Itemcode, T0.LineStatus, T0.DocDate 'Line Close Date'
    FROM ADO1 T0
    INNER JOIN ADOC T1 ON T1.DocEntry=T0.DocEntry AND T1.ObjType='17'
    WHERE T1.DocNum LIKE '[%0\]%' AND T0.LineStatus = 'C'
    Thanks,
    Gordon

  • Error in Sales Transaction in CRM 4.0 ?

    Hi All,
    We are working on CRM 4.0 i have created a sales transaction in WEB and  transaction will see in CRM and it is getting downloaded to R/3.
    But when I go back to CRM and check Sales Transaction it is showing me error as "An error has occured in the system XYZCLNT100 while copying the document".
    And i have been check in SMQ1&SMW01 ..in both T codes there is no error ..
    How can i figure out this problem ?
    can anyone help me in this regard?
    Thanks in advance.

    Please look into note 490932 for any issues of this nature
    This note gives an insight into possible error causes during the download or upload of sales transactions between CRM and R/3 and helps you correct these errors. This note is relevant for CRM Release3.0.
    It is also relevant for releases higher than 3.0.
    Other terms
    Download, initial, delta, delta download, SALESDOCUMENT, BUS_TRANS_MSG, event 00501014 501014
    Reason and Prerequisites
    The error causes may be included an incorrect configuration or missing system settings. The note only focuses on the sales transaction-specific configuration of the data exchange, but not on the settings for CRM Middleware in general or for other CRM Server applications.
    Solution
    In CRM Release 3.0, the following sales document items are transferred to the R/3 System:
    Sales items
    Customer return items
    Substitute delivery item
    Credit memo request items
    Debit memo request items
    As a leading system for the order entry, CRM only transfers data to the R/3 System if it is relevant for the logistical subsequent processing (delivery, billing). For this reason, requests for quotations and quotations themselves are not transferred to the R/3 back-end system with the standard delivery. With SAP note 455678, you can use a modification solution to also transfer quotations entered in CRM to the R/3 back-end system.
               Restrictions of note 455678:
    If you are using this solution, you cannot create any sales orders with reference to customer quotations in CRM.
    Mixed document processing (partially customer quotation items and partially sales order items) is not supported in the R/3 System and is therefore not possible during the quotation upload. The solution specified here only performs the upload for documents that consist of quotation items only.
    The quotation items must be defined in the Customizing for copying. This solution does not cover scenarios where the order is generated from the quotation as a result of a status change. Therefore, quotations entered in SAP Internet Sales (in particular) cannot be transferred to the R/3 System.
    Only completion rule 'A' ('Completed with one-time reference') is supported in the R/3 System.
    Sales transaction-specific settings for the data exchange
    1. Basic administrative settings for the replication of sales transactions
    a) The BDoc relevant for the distribution of all transaction types is called BUS_TRANSACTION_MESSAGE. In transaction SMOEAC, the relevant R/3 site must be subscribed to the corresponding publication 'All Business Transactions (MESG)' so that sales documents can be distributed to the R/3 back-end system. (To create a subscription, select the 'Subscription' object type in the 'Object type' selection list in transaction SMOEAC and then select the 'Object -> Create' function from the application menu or the corresponding symbol from the application function bar. The Subscription Wizard, which supports you during the creation of a new subscription, is started as a result.)
    b) Check to see whether the current CRM release has been maintained in the R/3 back-end system in the CRMPAROLTP table. This has to be taken into account in particular after an upgrade. You can maintain the CRMPAROLTP table in transaction SM30 in the R/3 back-end system:
                           Parameter name "CRM_RELEASE"
                           Param. value "30A"
    c) Event 00501014 must be activated in the R/3 back-end system so that the delta download of sales transactions from the R/3 back-end system to CRM works. The event must also be active for the upload of sales transactions from CRM to R/3.
    d) The event is activated automatically after a successful initial download. Call transaction R3AC4 ('Object Class Activation') in CRM and check whether the following entries exist:
                           Object class "BUSPROCESSND"
                           RFC destination <R/3 destination>
                           Select your entry and then choose 'Events by Object Class' (branch to the TBE31 table in the R/3 back-end system). The following entries must exist:
                           Event "00501014"
                           Obj. class "BUSPROCESSND"
                           Function "CRS_SALES_COLLECT_DATA"
                           If you do not see these entries, your initial download was not completed successfully.
    e) In transaction BD97 of your CRM system, the R/3 back-end system must have been maintained as the standard BAPI destination. Check the V_TBDLS view to see whether your R/3 back-end system has been defined as a logical system. A termination message in the SAPLCRM_ DISTRIBUTED_LOCKING program when you call a transaction in CRM indicates the missing destination assignment.
    Refer to notes 597812 and 674487. According to note 597812, the cross-system lock is processed using the RFC destination of the CRM middleware (SMOF_ERPSH table). However, the aforementioned entry in transaction BD97 for the Standard BAPI destination is still used to branch via the document flow to the R/3 system.
    f) In Release 3.1I, you can only have one entry for the RFCDEST field (RFC destination) in the CRMRFCPAR R/3 table.
    2. Definition of sales transaction-related Middleware parameters
    a) If you do not want a BOM explosion to occur for document items in CRM during the transfer to the R/3 back-end system, make the following settings in transaction R3AC6:
                           Key "R3A_SALES"
                           name "NOSTRUCTURE"
                           value "X"
                           This would make sense, for example, if you have already carried out a BOM explosion on the mobile client and if you do not want a new BOM explosion in the R/3 back-end system.
                           Make sure that the assigned item numbers in the sales transaction/sales document are set differently for main items and subitems so that no item numbers are assigned twice after the transfer and the BOM explosion in the R/3 System. The item numbers of the main items must be set identically in CRM and R/3. For more information, see note 496906.
                           Example:
                           CRM sales transaction
                           Pos.Nr.   Item No. Product
                           100 MAT1
                           200 MAT2
                           R/3 order
                           Pos.Nr.   Item No. Material
                           100 MAT1
                           101 Subitem1
                           102 Subitem2
                           103 Subitem3
                           104       ...
                           200 MAT2
                           You can maintain the item number assignment for the transaction types (CRM) or for the sales document types (R/3) in the Customizing.
    b) If a document is created in CRM and transferred to the R/3 back-end system, the warning messages of the transferred R/3 back-end document can also be displayed in the CRM document. In this way, you can recognize, for example, in the CRM document whether the transferred R/3 back-end document is incomplete and has to be postprocessed so that it can be further processed logistically. For this purpose, make the following settings in transaction R3AC6:
                           Key "R3A_SALES"
                           name "COLLECT_WARNINGS"
                           value "X"
    c) When you transfer a CRM document to R/3, you have the following control options with regard to pricing:
                           Key "R3A_SALES"
                           name "PRICINGTYPE"
                           value
                                             'B' = new pricing
                                             or
                                             'C' = copy manual pricecomponents,
                                             redetermine others
                                             or
                                             'G' = Copy price components unchanged,
                                             redetermine taxes (this value is
                                             delivered as a default setting)
    3. Definition of the R/3 dummy division in CRM
                  Note that no division exists in CRM in transactions at header level. In the R/3 order, however, the header division is a mandatory field. Thus, the R/3 dummy division must be maintained in CRM Customizing so that it can be determined during the transfer of a document. Otherwise, the order cannot be transferred to the R/3 back-end system.
                  Customizing path: 'Customer Relationship Management -> Master Data -> Organizational Management -> Division Settings -> Define Use of Division and Dummy Division'.
                  The use of several dummy divisions can be programmed in the CRM_DATAEXCH_AFTER_BAPI_FILL BAdI in the CRM_R3_SALESDOCUMENT_UPLOAD function module.
    Hints for the initial download
    Filter settings
    In transaction R3AC1, you set the filters for the initial/delta download of business objects. In the SALESDOCUMENT business object, you can set the filters for the order download from R/3 to CRM. For successful execution of the initial download, you have to set at least the VBAK-ERDAT filter criterion (document entry date) for the SALESDOCUMENT business object. This filter setting is required for the successful completion of order downloads.
    After you have completed these filter settings, you have to transfer these settings to the R/3 System. Select 'Filter sync.(R/3)'.
    Choose your R/3 System as a source site and check whether you are using the VBAK-ERDAT filter criterion:
    Example:
    Table/Structure Field OP Low
    VBAK ERDAT Greater than <Date>, for example, 20020128
    The date must be entered in the same form as it is stored on the database (YYYYMMDD)!
    The following filter criteria are also available:
    VBAK-AUART Sales document type
    VBAK-SPART Division
    VBAK-VBTYP Sales document category
    VBAK-VKORG Sales organization
    VBAK-VTWEG Distribution channel
    We recommend that you also use sales document numbers (VBAK-VBELN) as a further filter criterion. With this criterion, you can carry out an initial download according to sales document number intervals. The advantage of this filter criterion is that if your initial download terminates due to an error, you can restart the download after correcting the error as of the sales document number for which the error occurred. In this way you avoid having to restart a download for sales documents that have already been replicated.
    Example:
    Table/Structure   Field          OP            Low           High
    VBAK             VBELN          zwisch.        0005000000    0005099999
    Enter the field contents in the same way as it is stored on the R/3 database (leading zeros).
    If you want to use this filter criterion, go to transaction SM30 and make the following entry in the SMOFFILFLD table:
    Object name Table/Structure name Field name
    SALESDOCUMENT VBAK VBELN
    Note 497327 deals with possible filter-specific problems during the delta download that can occur due to missing R/3 back-end entries.
    Block size
    In this context, the block size specifies how many documents are selected in a transaction and transferred to CRM as a BDoc. The block size is defined on the system. The default value may have to be set to a lower value if problems occur (for example, memory overflow during the selection in the R/3 System). If the initial download terminates, check the dump log in the R/3 System (transaction ST22). The TIME_OUT or STORAGE_FREE_FAILED runtime errors indicate that the block size is too large. In this case, reduce the block size and restart the download.  In addition, you can clarify with your Basis Administration whether the rdisp/max_wprun_time kernel parameter is large enough (this avoids a TIME_OUT error).
    Basically, you should only download a few documents during the first download to check whether the system settings are correct. In this way, you can identify possible Customizing errors and correct them before the large load.
    Queue processing during the initial download
    In the case of very large transfer data sets, it may make sense to process the initial download in parallel within one object (object-internal parallel initial download) to complete the initial data transfer faster. Note 350176 describes the corresponding procedure.
    Queue processing during the upload/delta download
    Queues in CRM are defined in the SMOFQFIND table (for example, from CRM to CDB or from CRM to R/3).
    For the BUS_TRANS_MSG BDoc type, the default setting of the queue processing is that all orders for a customer are processed in one queue.
    As an alternative, you can set the queue processing in such a way that each order is processed in a separate queue. As a result, an individual order can no longer block the processing of other orders if an upload problem has occurred.
    If you prefer this queue processing, go to transaction SM30 and make the following change in the SMOFQFIND table:
    Select the BUS_TRANS_MSG BDoc type and change the segment field name from QUEUE_NAME to OBJECT_ID.
    In the same way, you can also set the queues for the delta download in the R/3 back-end system in such a way that each order is processed in a separate queue. If you prefer this queue processing, go to transaction SE16 in the R/3 back-end system and make the following change in the CRMQNAMES table:
    Select the entry for the SALESDOCUMENT object and change the BAPIFLD field from SOLD_TO to DOC_NUMBER (with BAPIOFFSET=3 and BAPIFLDLEN=10). Leave the second entry for the SALESDOCUMENT object (with QOBJPART=SAL_ERR) unchanged.
    In transaction SMQR, check to see whether the queues have been registered or check transaction SMQS to see whether the destinations have been registered because otherwise, the queues are not processed automatically, and this can lead to queue overloads.
    Check the queues regularly.
    Composite SAP Note 504090 covers all notes that solve known problems in the transfer as of Support Package 06 (SP06).
    Document cannot be maintained in online mode
    If you cannot maintain a document, this can have various reasons. Basically, a sales document entered in CRM is locked until the R/3 System has confirmed the update of the order successfully.
    If message CRM_ORDER019 "Document will be distributed - changes are not possible" occurs in CRM, check the queues (transaction SMQ1 and SMQ2). To analyze the data exchange from CRM to R/3, refer to note 431345.
    If message CRM_ORDER013 "Transaction &1 is being processed by user &2" occurs in CRM or if message V1042 "Sales document &1 is currently being processed (by user &2)" occurs in R/3, the document is processed in the other system respectively. To avoid inconsistencies, a cross-system lock is set during the processing of a replicated transaction so that the document cannot be processed simultaneously in two systems.
    Other notes
    Only error-free sales documents are distributed to the R/3 System. If, in R/3, you change a sales document that was originally created in CRM, these changes are not transferred to CRM. That is, you should always make the changes in the original CRM document to ensure the consistency of the document data in both systems. Sales documents entered in the R/3 System are transferred to CRM, but they are locked for processing there. Changes to a document created in R/3 are also transferred to CRM.
    In your settings for the data exchange, also make sure that the document number ranges correspond in both systems. For the successful sales document exchange between the systems, the transaction types and item categories have to be created in exactly the same way in both systems. If these objects do not exist in one system, you have to create them manually.
    In transaction CRMM_BUPA_MAP, you can determine into which R/3 customer number the CRM business partner is converted and vice versa. If you do not receive a conversion for the specified business partner here, this indicates that a transfer problem has not occurred in the sales document but during the business partner download.
    Header Data
    Release Status: Released for Customer
    Released on: 02.05.2006  15:04:13
    Priority: Recommendations/additional info
    Category: Consulting
    Primary Component: CRM-BTX-BF-IF R/3 Interface for Business Transactions

  • What table where i can find the errors in Sales Order

    hi,
    what table where i can find the errors in Sales Order. here's my situations, I need to create a abap report of CRM sales order not replicated to R/3 and show what's the error. I can't find the actual error in CRMD_ORDDERADM_H and CRMD_ORDERADM_I. I also tried calling program "CRM_ORDER_READ" but the program doesn't display/returns error's on header and item level.
    please help.
    earl g. faren

    hi,
    what i need is a table where i can find the sales transaction errors. I'm doing a abap report to list down sales transactions with error(s). I checked the table CRMD_ORDERADM_H and CRMD_ORDERADM_I but there's no field for transaction errors.
    please help me find a table where I can link the tables above to get the specific errors for a sales transactions.
    thanks alot.

  • Itm cat Error in sales order

    Gurus,
    I am facing an error in sales order creation.
    When I enter the material and qty and press enter, I am getting an error saying the Item category is not defined.
    have anyone came across this error, kindly help

    HI,
    Generally item category is determined by the combination of
    sales doc type + item cat grp +usage + high level itm cat(if any).
    so check whether the above requirements are fulfilled i.e  for the sales doc type (if customised) and item category (maintained in mat master sales org-2) are maintained in VOV4 or not.
    Reward points if helpful.
    regards,
    gupta.

  • CRM - automated error monitoring tools to track errors in sales orders

    could you please let me know whether we have any
    automated error monitoring tools to track errors in sales orders
    Thanks in advance

    I wont recommend turning off cookies in production.
    Turning off cookies was only from a Performance
    Testing perspective, Not using cookies for a performance test but using them in production, sort of invalidates the test, since much of the issue I had was the testing tool waiting for data to be returned to the cookies so it could be used to move to the next page.
    Partner Management uses all of them. I uses iStore for its external launch page, OA framework for its functionality, but then links to Sales online for Opportunities, and Quotes which I believe is AK framework. so you have a mixture of several
    frameworks involved...... plus Discoverer Viewer...

  • Pricing Error on Sales order :Critical:

    Hi all,
    I'm creating a sales order,  where in I'm getting Pricing Error.
    Condition record is maintained for PR00 in USD
    It is getting populated but showing red signal.
    VPRS also showing Red signal. If I go in analysis of VPRS , it shows message exchage rate error. But Company code currency & document currency is same USD.
    so It should not give this error.
    But If I go to customer master & in sales area tab & maintain currency as USD, then there is no error in Sales order. All is fine.
    But logically , system should not ask the exchage rate as Company code & document currency both are USD.
    I expect some quick replies as we are now in impact analysis & on verge of go live next month.

    Thats what I mention in previous post that
    Its a standard beheviour, Document currency is proposed/determined in sales order or billing doc on the bases of customer master record of the Sold-to Party.
    And exchange rate for same currency is out of question.
    Thats why, when maintain curreny in customer master (Sold-to Party), you don't get error.
    As, system is able determine/propose a currency for document currency.
    Further, what you can do is press F1 button on the following fie,lds for more clarification.
    > Sales Order - Header  - Sales Tab - Pricing & Statistics Section - Doc. Currency Field
    > Customer Master - Sold-to Party - Sales Data - Sales Tab - Currency Field
    I hope that clarifies.
    Regards
    JP

  • Error on Sales Order - u201Cyou cannot open rows in the document"

    Hi everyone,
    Does anyone have any idea why this error would be occuring when a user tries to add a sales order?
    u201Cyou cannot open rows in the document [sales order u2013Rows u2013 Rows status] [line0] [Message131 -194]?
    If the user closes the sales order and then recaptures it, the sales order goes through. As you can imagine, the order clerks are getting a bit angry when their large orders have to be closed.
    Thanks.
    Kind regards,
    Simon Carolin

    Hi
    If it is affecting your business severly ,log a support to SAP .Meanwhile ,
    Lets start some troubleshooting your system
    1.Are you using formatted search in Sales Order
    2.Are  you using sp_transaction notification
    3.Did you do any changes in your system recently like upgrade ,
    4.Is it happen only to certain item or BP
    Hint :
    1.Disable all addon
    2.Disable your formatted search
    3.Disable sp_transaction notification
    4.Try to create a sales order and .,
    Does error occur again? Please also specify your SBO version and Patch level
    <Note> Try test your issue  test environment
    This will help to narrow down
    Thank you
    Bishal

  • Error in Sales InvoiceSAP ERROR A/R INVOICE- ROWS [BASE DOCUMENT INTERNAL ID] "NO MATCHING RECORD FOUND"

    Hi,
    I am new to this portal.
    When I am trying to add A/R invoice based on Sales Order I got this Error Message from Evening in All Open Document. How to Rectify This.
    An Early Response Will Be very helpful.
    Thanks,
    Vikram

    Hello Vikram,
    Welcome to the Portal. Please check whether the Item Code and other line level Items on Sales Order are same or not.
    This type of message generally occurs when Base Document Rows Level are different from Target Document.
    Hope this Help
    Sudhir Sharma

  • Batch updation error from Sales Order

    Hi All,
    I am facing a problem in my addon while Adding/Updating Sales Order.
    In my addon, after adding or updating Sales Order, checking the Pval.ActionSuccess property , I am updating the batch allocation for the quantity in the order into IBT1 using DI API.  It was working nice. But in one company database it is causing issue. Sales Order is getting added/updated. But after that when the batch is updated using DI API, it is showing the error below.
    Another user has altered the quantity of batch 000001
    in Whse 01 in row 1  [(----) 29-9]
    Please help me in this issue.
    Jisha

    Hi Jisha,
    I would change the trigger on which you decide to change the batch. You may correct me if I am wrong, if you wait for a pVal.ActionSuccess, I'd say this is a user interface action. Maybe there is a timing difference. When you are waiting for DI-API to complete I try something like this:
    RetVal = Order.Add()
                            If RetVal = 0 Then
                                 'You Batch actions here
                            End if
    Hope this helps.
    Kind regards,
    Winfried Tiemessen

Maybe you are looking for